WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because Windows paths are mishandled during certain validation
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.5% (FIRST EPSS); higher than 91.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: wordpress (Debian:10) 5.0.17+dfsg1-0+deb10u1; wordpress (Debian:12) 5.2.4+dfsg1-1; wordpress (Debian:8) 4.1.28+dfsg-0+deb8u1.
Add it to your regular patch cycle. Upgrade to wordpress (Debian:10) 5.0.17+dfsg1-0+deb10u1; wordpress (Debian:12) 5.2.4+dfsg1-1; wordpress (Debian:8) 4.1.28+dfsg-0+deb8u1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because Windows paths are mishandled during certain validation of relative URLs.
- Published
- Oct 17, 2019
- Updated
- Jun 16, 2026
- EPSS
- 4.5% · 91th percentile
- CWE
- CWE-918
Report tools
Action score
40
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.5%
Is WordPress on your site?
WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wordpress | wordpress | cpe:2.3:a:wordpress:wordpress |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Using wordpress? Add it to your stack and be the first to know about CVEs like this one. (WordPress)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wordpress wordpressbefore 5.2.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:10 | wordpress | before 5.0.17+dfsg1-0+deb10u1 | 5.0.17+dfsg1-0+deb10u1 |
| Debian:12 | wordpress | before 5.2.4+dfsg1-1 | 5.2.4+dfsg1-1 |
| Debian:8 | wordpress | before 4.1.28+dfsg-0+deb8u1 | 4.1.28+dfsg-0+deb8u1 |
| Debian:9 | wordpress | before 4.7.18+dfsg-1+deb9u1 | 4.7.18+dfsg-1+deb9u1 |
Same product
wordpress: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-87902An unauthenticated attacker can make `get_page_template()` page-template resolution include a chosen readable local `.php` file outside the KEV74This week
- CVE-2026-63030WordPress < 7.0.2 - REST API batch-route confusion and SQL injection issue leading to Remote Code ExecutionKEV72This week
- CVE-2026-60137WordPress < 7.0.2 - Facilitated SQL Injection via author__not_in in WP_QueryKEV60This week
Published before and after this one in the same product
- ← EarlierCVE-2019-16223Sep 11, 2019 · WordPress before 5.2.3 allows XSS in post previews by authenticated users.23Monitor
- ← EarlierCVE-2019-17669Oct 17, 2019 · WordPress before 5.2.4 has a Server Side Request Forgery (SSRF) vulnerability because URL validation does not consider the interpretation of41Plan
- Later →CVE-2019-17671Oct 17, 2019 · In WordPress before 5.2.4, unauthenticated viewing of certain content is possible because the static query property is mishandled.32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:wordpress | 5.2.4+dfsg1-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- core.trac.wordpress.org/changeset/46472
- github.com/WordPress/WordPress/commit/9db44754b9e4044690a6c32fd74b9d5fe26b07b2
- lists.debian.org/debian-lts-announce/2019/11/msg00000.html
- lists.debian.org/debian-lts-announce/2020/09/msg00011.html
- lists.debian.org/debian-lts-announce/2022/10/msg00010.html
- wordpress.org/news/2019/10/wordpress-5-2-4-security-release/
- wpvulndb.com/vulnerabilities/9912
Vendor advisories and official records. Exploit/PoC links are deliberately left out.