How to verify CVE-2025-7205
Confirm whether your systems are actually affected — run the exact detection check below (Nuclei command or OpenVAS NVT). Detection only; it does not exploit.
How to verify this vulnerability
Scanner data tells you how to confirm whether your systems are actually affected — not just that the CVE exists. Run a Nuclei template against your target for a yes/no answer in seconds.
nuclei -t CVE-2025-7205-give-39e501d8-88a0-4625-aeb0-aa33fc89a8d4.yaml -u https://your-target -rl 50 -timeout 10Community template — download the YAML from GitHub first, then run the command against your own host.
- lowCommunityhttpGiveWP – Donation Plugin and Fundraising Platform <= 4.5.0 - Authenticated (GiveWP worker+) Stored Cross-Site Scripting GitHub ↗
Find every CVE you can verify
Search the whole database by Nuclei coverage — filter by vendor, severity and KEV to build a verification list for your entire stack.
- Filter all CVEs that ship a Nuclei template
- Combine with vendor, severity & KEV
- Build a scan list across your stack
This template is on GitHub already — an account lets you search and filter every CVE that has one, not just this CVE.
Verify with OpenVAS
Greenbone/OpenVAS ships 1 NVT check for CVE-2025-7205. OpenVAS detects this CVE by NVT OID — enable the NVT in your scan config, or confirm it is in your feed with the query below.
gvm-cli socket --xml "<get_nvts nvt_oid='1.3.6.1.4.1.25623.1.0.133050' details='1'/>"1.3.6.1.4.1.25623.1.0.133050since 2026-06-25