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

CVE-2024-27955

HIGH · 8.8 CVSS v3.1 Published 2024-05-17
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
Cross-Site Request Forgery (CSRF) vulnerability in WP Automatic Automatic allows Privilege Escalation.This issue affects Automatic: from n/a through 3.92.0.

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

Cross-Site Request Forgery (CSRF) vulnerability in the WP Automatic plugin allows remote attackers to perform privilege escalation by tricking authenticated administrators into unknowingly submitting malicious requests, potentially enabling unauthorized administrative actions.

MitigationUpgrade WP Automatic to version 3.92.1 or later to obtain the vendor patch. Additionally, implement anti-CSRF tokens (nonce validation) on all state-changing operations and ensure proper SameSite cookie attributes.

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 WP Automatic plugin is installed
    Locate the wp-automatic directory in wp-content/plugins/ or check via WordPress admin plugins page
    Affected if The plugin directory exists and the plugin appears in the installed plugins list
  2. Confirm WP Automatic version
    Check the plugin main file (wp-automatic.php) for the Version header, or view the plugin details in WordPress admin under Plugins > Installed Plugins
    Affected if The installed version is prior to 3.92.1 (the fixed release)
  3. Verify plugin is active
    Check if WP Automatic appears in the list of active plugins in WordPress admin or in the wp_options table under active_plugins
    Affected if The plugin is actively enabled on the site
  4. Check for admin session exposure risk
    Review whether the site has administrators who could be tricked into clicking malicious links while authenticated (examine access logs for suspicious admin-initiated requests to plugin endpoints)
    Affected if Administrators regularly access the WordPress admin panel and the plugin handles state-changing operations

The environment is affected if WP Automatic plugin versions prior to 3.92.1 are installed and active, exposing authenticated administrators to CSRF-based privilege escalation attempts.

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

Upgrade WP Automatic to version 3.92.1 or later to obtain the vendor patch. Additionally, implement anti-CSRF tokens (nonce validation) on all state-changing operations and ensure proper SameSite cookie attributes.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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