dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-13815

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-05
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 The Listingo theme for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 3.2.7. 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 · moderate confidence

The Listingo WordPress theme fails to properly validate user input before passing it to do_shortcode(), allowing unauthenticated attackers to execute arbitrary shortcodes. This functionality abuse could expose sensitive data, escalate privileges, or inject malicious content.

MitigationUpdate Listingo theme to version 3.2.8 or later where the vulnerability is patched; alternatively, implement input validation before do_shortcode() calls or deploy a WAF to block malicious shortcode requests.

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. Confirm Listingo theme is installed
    Navigate to Appearance > Themes in WordPress admin panel and verify Listingo theme is present and active
    Affected if Listingo theme is installed and active
  2. Identify Listingo theme version
    Check the style.css file in wp-content/themes/listingo/ or view theme details in WordPress admin under Appearance > Themes > Listingo > Theme Details
    Affected if Version is below 3.2.8 (vulnerable versions)
  3. Locate vulnerable do_shortcode calls
    Search theme PHP files for 'do_shortcode(' patterns, particularly in files handling user input such as search, filter, or submission forms
    Affected if Code passes $_GET, $_POST, or request parameters directly to do_shortcode() without sanitization
  4. Test unauthenticated shortcode execution
    Send a crafted request to common shortcode endpoints (e.g., ?s=[shortcode], query parameters used by theme shortcodes) with a benign test shortcode like [test]
    Affected if The shortcode executes and output appears in the response without authentication
  5. Review shortcode handler functions
    Examine includes/core/theme_shortcodes.php or similar files in the theme for functions that accept and process shortcode attributes from user input
    Affected if Shortcode functions use raw user input in attributes without validation

A user is affected if Listingo theme version is below 3.2.8 AND the theme processes user input through do_shortcode() without sanitization, allowing unauthenticated shortcode execution.

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 Listingo theme to version 3.2.8 or later where the vulnerability is patched; alternatively, implement input validation before do_shortcode() calls or deploy a WAF to block malicious shortcode requests.

Recommended fix Moderate confidence

Listingo theme version 3.2.8 or later

  1. Update the Listingo theme to the latest version available from the theme developer (ThemeForest or the theme vendor)
  2. After updating, verify that the shortcode execution vulnerability is patched by confirming the theme vendor has released a version after 3.2.7
  3. If automatic updates are not available, manually upload the new theme version via WordPress admin panel under Appearance > Themes
  4. Verify the WordPress site functions normally after the theme update
Caveat Review theme changelog for any breaking changes or required configuration adjustments after upgrading

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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