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

CVE-2024-12454

MEDIUM · 6.1 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 →
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 Affiliate Program Suite — SliceWP Affiliates plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.23. This is due to missing or incorrect 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 SliceWP Affiliates WordPress plugin versions up to 1.1.23 has a function with missing or incorrect nonce validation, allowing unauthenticated attackers to forge administrative requests that can inject malicious web scripts if a site administrator clicks a crafted link.

MitigationUpdate the SliceWP Affiliates plugin to version 1.1.24 or later which includes proper nonce validation 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
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. Locate SliceWP Affiliates plugin installation
    Check if the plugin files exist in your WordPress installation at wp-content/plugins/slicewp/ or via WordPress admin under Plugins > Installed Plugins
    Affected if The plugin directory 'slicewp' exists in wp-content/plugins/ or the plugin appears in WordPress admin plugins list
  2. Identify installed plugin version
    Open the main plugin file (usually slicewp.php) in wp-content/plugins/slicewp/ and locate the 'Version' header in the plugin comment block, or check the version column in WordPress admin Plugins page
    Affected if Version displayed is 1.1.23 or lower
  3. Confirm plugin is active
    Check WordPress admin > Plugins > Installed Plugins to verify SliceWP Affiliates shows as 'Active'
    Affected if Plugin is active and version is 1.1.23 or lower
  4. Verify vulnerability is exploitable
    The vulnerability is a CSRF (Cross-Site Request Forgery) flaw where missing nonce validation allows forged requests. Since the issue is in the code structure (missing nonce check), any active installation of version 1.1.23 or below is potentially affected when an administrator interacts with a crafted link
    Affected if Plugin version is 1.1.23 or lower and the plugin processes administrative actions without requiring nonce token verification

You are affected if SliceWP Affiliates plugin is installed, active, and running version 1.1.23 or lower - this version lacks proper nonce validation in a function, allowing unauthenticated attackers to forge administrative actions via CSRF.

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 SliceWP Affiliates plugin to version 1.1.24 or later which includes proper nonce validation to prevent CSRF attacks.

Recommended fix Moderate confidence

SliceWP Affiliates version 1.1.24 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'SliceWP Affiliates' (or 'Affiliate Program Suite — SliceWP Affiliates') plugin
  4. If an update is available, click 'Update Now' to update the plugin to version 1.1.24 or later
  5. Verify the plugin version after update to confirm the fix is applied

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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