CVE-2022-1591 json
WordPress Ping Optimizer < 2.35.1.3.0 - Arbitrary Settings Update via CSRF
published 4y ago modified 4mo ago also EUVD-2022-24881
- cvss
- 4.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
The WordPress Ping Optimizer WordPress plugin before 2.35.1.3.0 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack
Patch / fix
- wordpress_ping_optimizer_project wordpress_ping_optimizer 2.35.1.3.0
Is CVE-2022-1591 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/b1a52c7e-3422-40dd-af5a-ea4c622a87aa referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
Affected products
- Unknown WordPress Ping Optimizer
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
-
wpscan.com
/vulnerability/b1a52c7e-3422-40dd-af5a-ea4c622a87aa
exploit, patch, third-party-advisory
Sources
- CVE List CVE-2022-1591
- NVD CVE-2022-1591
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.