Radar sectionsDatabase
Check my site
WordPress plugin

OOPSpam Anti-Spam <= 1.1.44 — Cross-Site Request Forgery via empty_ham_entries and empty_spam_entries

CVE-2023-35913Published · Updated

Action summary

Affected: <1.1.45Update to 1.1.45 or newer

All remediation steps
Severity
Medium5.4
CVSS
5.4
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:R User interaction
Required
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:L Availability
Low
Weakness
CWE-352 CSRF
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) oopspam-anti-spam

  1. Affected< 1.1.45
  2. Patched in1.1.45

Update to 1.1.45 or newer.

You are affected if you run < 1.1.45. Version 1.1.45 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA).
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 1.1.45, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA) to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Skalucy.

The OOPSpam Anti-Spam plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.1.44. This is due to missing or incorrect nonce validation on the 'empty_ham_entries' and 'empty_spam_entries' functions. This makes it possible for unauthenticated attackers to delete both spam and legitimate entries via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA)

All 4
More vulnerabilities in oopspam Anti-Spam: Spam Protection for WordPress Forms & Comments (No CAPTCHA)
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting
≤1.2.62Update to 1.2.63
CVE-2026-32544
Medium5.3Unauthenticated IP Header Spoofing
≤1.2.53Update to 1.2.54
CVE-2025-12094
Medium5.5Authenticated (Admin+) Stored Cross-Site Scripting
≤1.1.35Update to 1.1.36
CVE-2023-22716

Same weakness (CSRF)

All CSRF
Other CSRF vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity medium, CVSS 5.4

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?