CVE-2024-32693
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in ValvePress Automatic.This issue affects Automatic: from n/a before 3.93.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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the ValvePress Automatic plugin (WordPress) allows remote attackers to trick authenticated users into performing unintended actions on the affected site. The flaw exists due to missing or insufficient CSRF protections in affected versions before 3.93.0.
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
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Automatic plugin is installedLog into WordPress admin panel and navigate to Plugins > Installed Plugins, or inspect /wp-content/plugins/ directory for the 'automatic' plugin folder. If the plugin is not present, you are not affected.Affected if The ValvePress Automatic plugin is installed on the WordPress site.
-
Check installed plugin versionIn WordPress admin, find the Automatic plugin listing and note the version number displayed. Alternatively, open the main plugin file (usually automatic.php or class-automatic.php in the plugin directory) and locate the 'Version' header in the file comments.Affected if The installed version is lower than 3.93.0 (for example, 3.92.x, 3.91.x, or earlier).
-
Inspect plugin for CSRF token implementationExamine the plugin PHP files for presence of wp_nonce_field(), wp_nonce_url(), or check_admin_referer() function calls around form submissions and admin action handlers. Look for nonce verification in state-changing functions.Affected if Forms and admin action handlers lack nonce verification calls, or nonce checks are missing entirely.
-
Test for CSRF vulnerability (if authorized)Create a malicious HTML page that submits a form targeting your WordPress admin area with an action like ?action=some_automatic_function. Host it on another domain and attempt to trigger it while logged into WordPress. Use browser developer tools to verify if the action executes without a CSRF token prompt.Affected if The target action executes successfully without requiring a unique CSRF token or referrer validation.
You are affected if the Automatic plugin is installed with a version lower than 3.93.0 and lacks proper CSRF token verification on sensitive admin actions.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Automatic plugin to version 3.93.0 or later. Additionally, implement anti-CSRF tokens on all state-changing operations and consider enabling SameSite cookie attributes as defense-in-depth.
3.93.0
- Backup your WordPress site database and files before updating
- Update the ValvePress Automatic plugin to version 3.93.0 or later
- Verify the plugin version has been successfully updated in WordPress admin dashboard
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32693 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-32693 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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