CVE-2025-52790
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in r-win WP-DownloadCounter wp-downloadcounter allows Stored XSS.This issue affects WP-DownloadCounter: from n/a through <= 1.01.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCSRF vulnerability in WP-DownloadCounter plugin allows attackers to craft malicious requests that, when triggered by an authenticated administrator, can inject and store malicious JavaScript (Stored XSS) into the application. The lack of anti-CSRF tokens on state-changing operations enables this attack.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if WP-DownloadCounter plugin is installedNavigate to WordPress admin > Plugins and look for 'WP-DownloadCounter' in the installed plugins list, or inspect the /wp-content/plugins/ directory for a folder named 'wp-downloadcounter' or similarAffected if The plugin appears in the installed plugins list or filesystem
-
Identify installed plugin versionIn WordPress admin > Plugins, find WP-DownloadCounter and view the version number displayed under the plugin name, or check the plugin's main PHP file for a 'Version' header commentAffected if A version number is displayed and can be compared to patched versions
-
Confirm plugin is activeIn WordPress admin > Plugins, check if WP-DownloadCounter shows as 'Active' rather than 'Inactive' or 'Must-Use'Affected if The plugin is currently activated on the site
-
Inspect for CSRF token implementationAccess the plugin's admin PHP files (typically in the plugin folder under wp-admin or includes) and search for nonce verification functions like 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' on state-changing forms (settings, save, update, delete actions)Affected if State-changing operations lack nonce verification or anti-CSRF token checks in the code
Your environment is affected if WP-DownloadCounter is installed, active, and the installed version lacks CSRF protection on administrative actions that can lead to stored XSS injection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to a patched version of WP-DownloadCounter when available. Until then, disable the plugin or implement web application firewall rules to block CSRF attempts. Admin users should be educated not to click untrusted links.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52790 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-52790 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data