dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-12554

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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
The Peter’s Custom Anti-Spam plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.2.3. This is due to missing nonce validation on the cas_register_post() function. This makes it possible for unauthenticated attackers to blacklist emails via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 · high confidence

The Peter's Custom Anti-Spam WordPress plugin lacks nonce validation on the cas_register_post() function, allowing unauthenticated attackers to submit forged requests that blacklist email addresses. Successful exploitation requires tricking a logged-in administrator into clicking a malicious link, leveraging the site's authenticated session.

MitigationUpdate the plugin to the latest version beyond 3.2.3 and implement proper nonce validation on the cas_register_post() function to prevent CSRF attacks.

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

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
None
Integrity
Low
Availability
Low

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

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 plugin installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins. Locate 'Peter\'s Custom Anti-Spam' and check the version number displayed. Compare this version against the known vulnerable versions (all versions prior to the fix in version 3.2.3).
    Affected if The plugin is installed and the version is lower than 3.2.3 (or the version cannot be determined and the plugin has not been updated recently).
  2. Confirm cas_register_post function exists
    Access the plugin files via FTP or file manager. Locate the main plugin file (typically cas.php or similar) and search for the function named 'cas_register_post'. Verify this function exists in the codebase.
    Affected if The cas_register_post() function is present in the plugin files.
  3. Inspect nonce validation in cas_register_post
    Open the plugin PHP file containing cas_register_post(). Examine the function code to determine if a nonce check is performed. Look for calls to wp_verify_nonce, check_admin_referer, or similar nonce validation functions at the beginning of this function.
    Affected if The cas_register_post() function exists and does NOT contain nonce validation (wp_verify_nonce, check_admin_referer, or similar) at the function entry point.
  4. Check blacklist functionality is accessible
    Examine the cas_register_post() function to confirm it handles email blacklisting operations. Verify the function processes POST or GET parameters related to email blocking without requiring authentication.
    Affected if The function processes email blacklist submissions and can be triggered without proper authentication tokens.

A user is affected if the Peter's Custom Anti-Spam plugin is installed with a version prior to 3.2.3 AND the cas_register_post() function lacks nonce validation, allowing CSRF attacks to blacklist emails via a forged request to a logged-in administrator.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version beyond 3.2.3 and implement proper nonce validation on the cas_register_post() function to prevent CSRF attacks.

Recommended fix Moderate confidence

3.2.4 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate "Peter's Custom Anti-Spam" in the plugin list
  4. 4. If an update is available, click "Update Now" to upgrade to the latest version
  5. 5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org/plugins/peters-custom-anti-spam
  6. 6. After upgrading, verify the plugin is running version 3.2.4 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12554 — 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-2024-12554 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