CVE-2024-13812
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 · uneditedThe The Anps Theme plugin plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 1.1.1. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.
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 confidenceThe Anps Theme plugin for WordPress fails to validate user input before passing it to the do_shortcode() function, allowing unauthenticated attackers to inject and execute arbitrary WordPress shortcodes. This shortcode injection vulnerability enables attackers to potentially access sensitive data, inject malicious content, or perform actions on behalf of the site.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Anps Theme plugin versionIn WordPress admin, go to Appearance > Themes and click on the Anps Theme to view its details, or check the style.css file in wp-content/themes/anps theme name folder for the Version: headerAffected if Installed version is any version prior to the patched release (verify against official WordPress plugin repository for latest patched version)
-
Check for shortcode-related query parameters in web logsReview HTTP access logs (typically in /var/log/apache2/ or /var/log/nginx/) for requests containing parameters like 'shortcode', 'sc', or content that looks like WordPress shortcode syntax (e.g., [square brackets with text]) in query strings or POST bodiesAffected if Unusual shortcode syntax patterns appear in incoming requests to your site
-
Inspect for unauthorized shortcode output in posts/pagesSearch WordPress database via phpMyAdmin or wp cli for posts containing unexpected shortcode patterns: SELECT * FROM wp_posts WHERE post_content LIKE '%[%' AND post_status='publish'Affected if Published content contains shortcodes you did not intentionally add, especially ones that access sensitive data (e.g., contact forms, galleries, user info)
-
Verify shortcode callback functions are not externally accessibleCheck if the theme or plugin exposes any AJAX endpoints or direct URL parameters that directly invoke do_shortcode() without admin privilege checks; review theme files in functions.php for do_shortcode calls on $_GET or $_POST inputAffected if The theme directly passes request parameters to do_shortcode without sanitization or capability checks
You are affected if the Anps Theme plugin is installed and its version predates the patched release, or if you observe unauthorized shortcode injection attempts in logs or published content.
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 dataUpdate the plugin to the latest patched version immediately. If no patch is available, disable the plugin and implement a WAF rule to block requests attempting to exploit shortcode execution parameters.
- 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-13812 — 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-13812 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