CVE-2025-52790: WP-DownloadCounter · Cross-Site Request Forgery (CSRF)
Affects WP-DownloadCounterSource CVE Database V5
Not known to be exploited · CVSS 7.1 High.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 20 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| r-win WP-DownloadCounter | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, users should consider disabling the plugin or restricting access to trusted users only. Applying web application firewall (WAF) rules to detect and block CSRF and XSS attempts may provide temporary mitigation.
Description
Cross-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.