dbcve.org
PressmartWordPress extension · Presslayouts

CVE-2024-13797

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to 1.2.17 or later.
See remediation →
100/100
Remediation priority · Urgent
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 PressMart - Modern Elementor WooCommerce WordPress Theme theme for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 1.2.16. 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 confidence

The PressMart WordPress theme up to version 1.2.16 fails to properly validate user input before passing it to WordPress's do_shortcode() function, allowing unauthenticated attackers to execute arbitrary shortcodes. This can lead to remote code execution depending on what shortcodes are registered on the site.

MitigationUpdate the PressMart theme to version 1.2.17 or later where proper input validation has been implemented. If no patch is available, consider disabling the theme or removing it until a fix is released.

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
PressmartWordPress extension
Affected:< 1.2.17

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

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

  1. Verify PressMart theme is installed
    In WordPress admin, go to Appearance > Themes to confirm PressMart theme is active or installed. Alternatively, check /wp-content/themes/pressmart/ directory exists.
    Affected if PressMart theme is present in the WordPress installation
  2. Identify installed theme version
    Check the style.css file in the theme directory for the 'Version:' header, or look in WordPress admin under Appearance > Themes > Theme Details.
    Affected if Version is displayed as less than 1.2.17
  3. Confirm vulnerable version range
    Compare the installed version against the affected range: any version below 1.2.17 is vulnerable.
    Affected if Installed version is 1.2.16 or lower
  4. Locate shortcode handler code
    Search theme files for do_shortcode() calls that use user-supplied input (GET/POST parameters) without sanitization. Common patterns include do_shortcode($_GET['shortcode']) or similar.
    Affected if Theme contains code that passes unsanitized user input directly to do_shortcode() function

You are affected if the PressMart theme version is below 1.2.17 and the theme exposes any endpoint that passes user input to do_shortcode() without validation.

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
Upgrade available Upgrade to 1.2.17 or later
Fixed in 1.2.17
Interim mitigation

Update the PressMart theme to version 1.2.17 or later where proper input validation has been implemented. If no patch is available, consider disabling the theme or removing it until a fix is released.

Recommended fix High confidence

PressMart theme version 1.2.17

  1. 1. Create a full backup of the WordPress site (database and files) before making any changes
  2. 2. Navigate to Appearance > Themes in the WordPress admin dashboard
  3. 3. Locate the PressMart theme and select the option to update to the latest version
  4. 4. Update to version 1.2.16 to 1.2.17
  5. 5. Verify the theme version shows 1.2.17 after the update
  6. 6. Test critical site functionality to ensure the update did not break existing features
Caveat Theme updates may override customizations; reapply any custom changes to child theme after upgrade

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

Fix this in Pressmart Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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