CVE-2023-0335: The WP Shamsi WordPress plugin through 4.3.3 has CSRF and broken access control vulnerabilities which leads us
CVE-2023-0335 is a medium-severity flaw (CVSS 6.5) affecting wp shamsi. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The WP Shamsi WordPress plugin through 4.3.3 has CSRF and broken access control vulnerabilities which leads user with role as low as subscriber delete attachment.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
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-0335?
wp shamsi: upgrade to newer than 4.3.3. Exact commands for each OS are on this page.
Is CVE-2023-0335 being exploited?
CVE-2023-0335 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-0335 affect?
CVE-2023-0335 affects wp shamsi. Severity is medium (CVSS 6.5). The WP Shamsi WordPress plugin through 4.3.3 has CSRF and broken access control vulnerabilities which leads user with role as low as subscriber delete attachment.
How urgent is CVE-2023-0335?
Priority 43/100. Public exploit reference
Software pages
Related CVEs
- CVE-2022-4555 MEDIUM 6.5 UPGRADE The WP Shamsi plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on
- CVE-2022-38058 MEDIUM 4.3 UPGRADE Authenticated (subscriber+) Plugin Setting change vulnerability in WP Shamsi plugin <= 4.1.1 at WordPress.