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

CVE-2024-11812

MEDIUM · 6.1 CVSS v3.1 Published 2024-12-20
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 Wtyczka SeoPilot dla WP plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.3.091. This is due to missing or incorrect nonce validation on the SeoPilot_Admin_Options() function. This makes it possible for unauthenticated attackers to update settings and 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 Wtyczka SeoPilot dla WP WordPress plugin versions up to 3.3.091 lacks proper nonce validation in the SeoPilot_Admin_Options() function, allowing unauthenticated attackers to forge administrative requests. This CSRF vulnerability enables attackers to modify plugin settings and potentially inject malicious web scripts (XSS) by tricking administrators into clicking crafted links.

MitigationUpdate the plugin to a patched version once available, or add proper nonce verification (wp_verify_nonce or check_admin_referer) to all state-changing operations in SeoPilot_Admin_Options(). Until patched, avoid clicking untrusted links while logged into WordPress admin.

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. Confirm SeoPilot plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'SeoPilot' or 'Wtyczka SeoPilot dla WP'. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'seopilot' in the name.
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, click on the plugin from the Plugins list and view the version number displayed, or check the plugin's main PHP file for a version constant or header comment.
    Affected if The version is 3.3.091 or any version up to and including 3.3.091
  3. Locate the SeoPilot_Admin_Options function
    Access the plugin files via FTP or file manager, then open the main plugin PHP file (typically named seopilot.php, seopilot-admin.php, or similar) and search for the function definition 'function SeoPilot_Admin_Options()'.
    Affected if The function exists in the plugin code
  4. Verify absence of nonce validation in the vulnerable function
    Within the SeoPilot_Admin_Options function code, search for 'wp_verify_nonce', 'check_admin_referer', or 'nonce' validation calls. Check if any form submissions or settings updates occur without these checks.
    Affected if The function processes settings changes (POST/GET requests) without verifying a nonce token
  5. Confirm admin access is required for exploitation
    While the vulnerability is CSRF (requires tricking an admin), verify that the SeoPilot_Admin_Options function is only accessible to users with administrator privileges by checking current_user_capability or role checks within the function.
    Affected if The function lacks proper capability checks AND nonce validation, allowing forged requests from authenticated admins

A user is affected if the SeoPilot plugin version is 3.3.091 or earlier AND the SeoPilot_Admin_Options() function processes settings without verifying a nonce token, enabling attackers to inject malicious settings or scripts via crafted links.

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

Update the plugin to a patched version once available, or add proper nonce verification (wp_verify_nonce or check_admin_referer) to all state-changing operations in SeoPilot_Admin_Options(). Until patched, avoid clicking untrusted links while logged into WordPress admin.

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