Full Auto Tags ManagerWordPress extension · Guillemantdavid
CVE-2023-34024
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 Guillemant David WP Full Auto Tags Manager plugin <= 2.2 versions.
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 WP Full Auto Tags Manager WordPress plugin versions 2.2 and below. The plugin lacks proper anti-CSRF token validation on state-changing admin actions (likely tag creation, modification, deletion, or settings updates), allowing authenticated administrators to be tricked into performing unintended operations via maliciously crafted requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Full Auto Tags ManagerWordPress extension
<= 2.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installationCheck if the WP Full Auto Tags Manager plugin exists in your WordPress installation at wp-content/plugins/guillemantdavid-full-auto-tags-manager/ or similar path containing 'full-auto-tags-manager'Affected if The plugin directory exists in your plugins folder
-
Check installed versionOpen the main plugin PHP file and look for the Version header in the plugin comment block, or check in WordPress admin under Plugins > Installed PluginsAffected if The reported version is 2.2 or lower, or if the Version header cannot be found indicating an old unversioned release
-
Identify admin action endpointsExamine the plugin PHP files for functions handling state-changing operations: look for hooks like admin_post_, wp_ajax_, or admin_menu/manage_options that handle tag creation, modification, deletion, or settings updatesAffected if The plugin contains admin action handlers for tags or settings without a clear nonce verification mechanism visible in the code
-
Verify nonce implementationSearch plugin source code for wp_verify_nonce, check_admin_referer, wp_create_nonce, or 'nonce' field validation in form processing logicAffected if The admin action handlers lack wp_verify_nonce or check_admin_referer calls, or nonce fields are missing from plugin forms and AJAX handlers that modify data
-
Confirm vulnerable attack surfaceReview all plugin forms and AJAX endpoints that perform database writes (insert/update/delete on tags or settings) and verify they do not validate a nonce token before processingAffected if Any form or AJAX endpoint that modifies plugin state does not validate a nonce token, creating a CSRF vulnerability
Your environment is affected if the WP Full Auto Tags Manager plugin version 2.2 or below is installed and its admin forms or AJAX actions handling tags or settings lack proper nonce token validation.
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.
From vendor dataImplement nonce/tokens on all forms and AJAX actions that modify plugin state, verify Origin/Referer headers server-side, and set SameSite attributes on session cookies.
Fix this in Full Auto Tags Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34024 — 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-2023-34024 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