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

CVE-2024-12555

MEDIUM · 6.1 CVSS v3.1 Published 2024-12-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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 SIP Calculator plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing nonce validation on a function. This makes it possible for unauthenticated attackers to inject malicious web scripts 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 SIP Calculator WordPress plugin (versions up to 1.0) lacks nonce validation on a critical function, enabling Cross-Site Request Forgery attacks. Unauthenticated attackers can craft malicious requests that, when triggered by an authenticated administrator clicking a crafted link, inject and execute arbitrary web scripts (stored XSS) within the plugin context.

MitigationAdd WordPress nonce verification (wp_verify_nonce or check_admin_referer) to all state-changing functions in the plugin, particularly the vulnerable function lacking validation. Verify all AJAX and form submissions include and validate nonces.

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

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

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 SIP Calculator plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate SIP Calculator; note the version number displayed. Alternatively, check the plugin header in sip-calculator.php or the main plugin file.
    Affected if The installed version is 1.0 or any version prior to 1.0, as these lack nonce validation on the vulnerable function.
  2. Identify state-changing functions in the plugin
    Examine the main plugin PHP file (typically sip-calculator.php or similar) and locate functions that process form submissions, update settings, or modify data. Common patterns: save/update/delete operations, settings handlers, AJAX action callbacks.
    Affected if The plugin contains functions that modify data or settings without first calling wp_verify_nonce(), check_admin_referer(), or similar nonce verification functions.
  3. Inspect AJAX handlers for missing nonce validation
    Search the plugin files for add_action('wp_ajax_') and add_action('wp_ajax_nopriv_') calls. For each handler, verify it includes a nonce check (wp_verify_nonce or check_admin_referer) before processing the request.
    Affected if Any AJAX handler processes requests without validating a nonce, particularly those accessible to administrators.
  4. Check form submissions for nonce fields
    Review PHP files handling form POST/GET requests. Look for form generation code (echo '<form') and verify that a nonce field is included (wp_nonce_field, wp_nonce_url) and validated on submission.
    Affected if Forms that modify plugin settings or data lack nonce field generation or do not verify nonces upon submission.
  5. Confirm the plugin lacks CSRF protection on sensitive operations
    Locate the specific function mentioned in the CVE as lacking validation. Examine this function to confirm it performs state-changing operations (data insertion, settings changes, script injection points) without any request verification.
    Affected if The vulnerable function processes requests without any CSRF token validation, allowing attackers to trick authenticated admins into executing unintended actions.

Your environment is affected if the SIP Calculator plugin is installed at version 1.0 or earlier AND the plugin code contains functions or AJAX handlers that process state-changing requests without verifying WordPress nonces.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add WordPress nonce verification (wp_verify_nonce or check_admin_referer) to all state-changing functions in the plugin, particularly the vulnerable function lacking validation. Verify all AJAX and form submissions include and validate nonces.

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-12555 — 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-12555 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