dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-12333

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
The Woodmart theme for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 8.0.3. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode through the woodmart_instagram_ajax_query AJAX action. 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 confidence

The Woodmart WordPress theme up to version 8.0.3 contains an arbitrary shortcode execution vulnerability in the woodmart_instagram_ajax_query AJAX action. The plugin does not properly validate user-supplied input before passing it to WordPress's do_shortcode function, allowing unauthenticated attackers to execute any registered shortcode on the site.

MitigationUpdate the Woodmart theme to version 8.0.4 or later which contains the security patch. If immediate update is not possible, consider disabling the theme's Instagram functionality or implementing a temporary web application firewall rule to block the vulnerable AJAX endpoint.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Woodmart theme installation
    Check your WordPress installation's wp-content/themes/woodmart folder, or look for 'Woodmart' in the WordPress admin under Appearance > Themes. Note the theme directory name and any version information visible in the theme details panel.
    Affected if The Woodmart theme is installed on the WordPress site
  2. Determine installed Woodmart version
    In WordPress admin, go to Appearance > Themes and click on the Woodmart theme to view its details, which typically displays the version number. Alternatively, check the style.css file in the theme folder for the 'Version' header comment.
    Affected if The version displayed is 8.0.3 or lower
  3. Verify AJAX endpoint accessibility
    Make a POST request to your site's wp-admin/admin-ajax.php endpoint with the action parameter set to 'woodmart_instagram_ajax_query'. For example: curl -X POST https://yoursite.com/wp-admin/admin-ajax.php -d 'action=woodmart_instagram_ajax_query'. A response indicates the endpoint is registered and accessible.
    Affected if The endpoint responds (does not return a 404 or access denied error), meaning the vulnerable AJAX action is available
  4. Confirm shortcode execution is possible
    Send a request to the same AJAX endpoint with a test shortcode in the parameter. For example: curl -X POST https://yoursite.com/wp-admin/admin-ajax.php -d 'action=woodmart_instagram_ajax_query&shortcode=[any_registered_shortcode]'. If the response contains the evaluated shortcode output rather than an error, arbitrary shortcode execution is possible.
    Affected if The shortcode provided is executed and its output appears in the response

If the Woodmart theme version is 8.0.3 or lower and the woodmart_instagram_ajax_query AJAX endpoint is accessible and processes shortcode parameters, the site is affected by this vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Woodmart theme to version 8.0.4 or later which contains the security patch. If immediate update is not possible, consider disabling the theme's Instagram functionality or implementing a temporary web application firewall rule to block the vulnerable AJAX endpoint.

Recommended fix Moderate confidence

Woodmart theme version 8.0.4 or later

  1. 1. Navigate to your WordPress dashboard
  2. 2. Go to Appearance > Themes
  3. 3. Locate the Woodmart theme
  4. 4. Check if an update to version 8.0.4 or later is available
  5. 5. If available, update the theme to the latest version
  6. 6. If no update is available through WordPress, download the latest version from ThemeForest and upload it manually
  7. 7. Verify the update was successful and test that the site functionality remains intact
Caveat Minor theme updates may include template changes; review child theme customizations after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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