PatchTheCVECVE-2023-6385: The WordPress Ping Optimizer WordPress plugin through 2.35.1.3.0 does not have CSRF checks in some places, whi
CVE-2023-6385 is a medium-severity flaw (CVSS 4.3) affecting wordpress ping optimizer. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 4.3 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | High |
| User interaction | Required |
| EPSS exploit chance | 0.2% (top 87%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2024-04-10 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2023-6385?
wordpress ping optimizer: upgrade to newer than 2.35.1.3.0. Exact commands for each OS are on this page.
Is CVE-2023-6385 being exploited?
CVE-2023-6385 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2023-6385 affect?
CVE-2023-6385 affects wordpress ping optimizer. Severity is medium (CVSS 4.3). 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.
How urgent is CVE-2023-6385?
Priority 23/100. Public exploit reference