CVE-2024-9837
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 AADMY – Add Auto Date Month Year Into Posts plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 2.0.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 AADMY WordPress plugin fails to validate user input before passing it to WordPress's do_shortcode() function, allowing unauthenticated attackers to inject and execute arbitrary shortcodes. This can lead to content injection, privilege escalation if admin shortcodes exist, or further site compromise.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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.
-
Confirm AADMY plugin is installedNavigate to WordPress admin dashboard > Plugins and look for 'AADMY' in the installed plugins list, or check the /wp-content/plugins/ directory for an 'aadmy' folder.Affected if The AADMY plugin folder exists in the WordPress installation.
-
Check installed versionIn the Plugins admin page, find the AADMY plugin and view its version number under the plugin name. Alternatively, check the main plugin PHP file for the 'Version' header in the plugin comments.Affected if The installed version is lower than 2.0.2 (versions before 2.0.2 are affected by this vulnerability).
-
Verify plugin is activeIn WordPress admin > Plugins, check if AADMY shows as 'Active'. For network/multisite, also check if network-activated.Affected if The plugin is active and accessible to unauthenticated users, making exploitation possible.
-
Identify vulnerable parameter or endpointReview the plugin's publicly accessible forms, shortcodes, or AJAX endpoints. Common triggers include frontend forms, search widgets, or any feature that processes user input through do_shortcode(). Check the plugin code for do_shortcode() calls with unsanitized $_GET, $_POST, or $_REQUEST variables.Affected if The plugin processes user-supplied input through do_shortcode() without validation, which is the vulnerable condition.
A site is affected if the AADMY plugin is installed, active, and running a version lower than 2.0.2, with an unprotected input pathway that passes user data to do_shortcode().
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 version 2.0.2 or later which contains proper input validation. If an update is unavailable, remove the plugin immediately to prevent exploitation.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9837 — 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-9837 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