The WordPress Ping Optimizer WordPress plugin through 2.35.1.3.0 does not have CSRF checks in some places, which could allow attackers to make logged in users perform unwanted actions via CSRF attacks such as clearing logs.
Product
wordpress-ping-optimizer vulnerabilities
2 published CVES affecting wordpress-ping-optimizer, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 2
- Critical
- 0
- High
- 0
- Medium
- 2
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress-ping-optimizer CVEs
Newest publication first
-
MediumCVSS 4.3 EPSS 0.22%
-
MediumCVSS 4.3 EPSS 0.35%
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
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.