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

CVE-2024-12322

HIGH · 8.8 CVSS v3.1 Published 2025-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The ThePerfectWedding.nl Widget plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.8. This is due to missing or incorrect nonce validation on the 'update_option' function. This makes it possible for unauthenticated attackers to update the 'tpwKey' option with stored cross-site scripting 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 ThePerfectWedding.nl Widget WordPress plugin lacks CSRF protection (nonce validation) on the update_option function handling the 'tpwKey' setting. This allows unauthenticated attackers to forge administrative requests that inject stored XSS into the tpwKey option by tricking admins into clicking malicious links.

MitigationUpdate the plugin to version 2.9 or later which includes proper nonce validation. Until patched, warn administrators against clicking untrusted links.

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
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 plugin installation and version
    In WordPress admin, go to Plugins > Instored Plugins and locate 'ThePerfectWedding.nl Widget'. Check the version number displayed. Alternatively, check the plugin main file header in wp-content/plugins/theperfectwedding-nl-widget/
    Affected if The installed version is lower than 2.9 or the version cannot be determined
  2. Confirm plugin is active
    Check the Plugins page in WordPress admin - the plugin must be both installed AND active for the vulnerability to be exploitable
    Affected if The plugin status shows as 'Active'
  3. Inspect the tpwKey option in database
    Access the WordPress database (via phpMyAdmin or wp-cli: wp option get tpwKey) and examine the current value stored in the 'tpwKey' option. Look for any suspicious script tags, HTML attributes, or encoded JavaScript payloads
    Affected if The tpwKey option contains unexpected HTML or JavaScript code, especially script tags or event handlers like onload/onerror
  4. Verify nonce validation is missing in source code
    Examine the plugin PHP files, specifically any handler for update_option or settings save functions. Search for wp_nonce_field, wp_verify_nonce, or check_admin_referer calls. The vulnerability exists if no nonce verification is performed before updating the tpwKey option
    Affected if The code handling tpwKey settings lacks nonce verification and directly processes requests without validating the request origin

A user is affected if the plugin version is below 2.9, the plugin is active, and either the tpwKey option contains malicious content or the code lacks nonce validation.

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 version 2.9 or later which includes proper nonce validation. Until patched, warn administrators against clicking untrusted links.

Recommended fix Moderate confidence

ThePerfectWedding.nl Widget version 2.9 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'ThePerfectWedding.nl Widget' in the plugin list
  4. Check if the current version is 2.8 or below
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Verify the plugin has been updated to a version newer than 2.8
Caveat Minor plugin updates typically do not introduce breaking changes; always review changelog before updating

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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