dbcve.org
Oopspam Anti SpamWordPress extension · Oopspam

CVE-2023-35913

HIGH · 8.8 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 1.1.45 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in OOPSpam OOPSpam Anti-Spam plugin <= 1.1.44 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in OOPSpam Anti-Spam plugin allows attackers to induce authenticated administrators to perform unintended actions by tricking them into visiting malicious URLs, potentially leading to spam filter configuration changes or other admin-level operations.

MitigationUpdate the OOPSpam Anti-Spam plugin to a version newer than 1.1.44, which should include proper CSRF token validation for state-changing requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Oopspam Anti SpamWordPress extension
Affected:< 1.1.45

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify OOPSpam Anti-Spam plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Locate OOPSpam Anti-Spam in the list. Alternatively, check the plugins directory (wp-content/plugins/oopspam-antispam/) exists on the server.
    Affected if The plugin is not installed or not present in the WordPress environment
  2. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify the OOPSpam Anti-Spam plugin shows as Active.
    Affected if Plugin is installed but not activated - CSRF requires the plugin to be active to be exploited
  3. Identify installed plugin version
    In WordPress admin, click on the plugin name in the plugins list to view version details. Alternatively, open the main plugin file (typically oopspam-antispam.php) in the plugin directory and locate the Version: header in the plugin comment block.
    Affected if Installed version is less than 1.1.45 (e.g., 1.1.44, 1.1.43, etc.)
  4. Review admin action logging
    Check WordPress activity logs or security audit logs for any suspicious admin-level actions originating from unexpected IP addresses or with unusual parameters, particularly changes to spam filter configuration.
    Affected if Unexpected configuration changes to spam settings are logged that were not performed by authorized administrators

A user is affected if the OOPSpam Anti-Spam plugin version is installed and active, and the version number is below 1.1.45.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.45 or later
Fixed in 1.1.45
Interim mitigation

Update the OOPSpam Anti-Spam plugin to a version newer than 1.1.44, which should include proper CSRF token validation for state-changing requests.

Recommended fix High confidence

OOPspam Anti-Spam version 1.1.45

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the OOPspam Anti-Spam plugin in the list
  4. Click 'Update Now' if an update is available, or manually update to version 1.1.45
  5. Verify the plugin version after updating to confirm version 1.1.45 is installed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Oopspam Anti Spam Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35913 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-35913 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data