dbcve.org
CreateWordPress extension · Catchthemes

CVE-2024-47356

MEDIUM · 5.9 CVSS v3.1 Published 2024-10-06
Fix available
A fix is available. Upgrade to 2.9.2 / 3.5.2 or later.
See remediation →
63/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in catchthemes Create create allows Stored XSS.This issue affects Create: from n/a through <= 2.9.1.

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

Stored Cross-site Scripting (XSS) vulnerability in the Create theme by catchthemes allows attackers to inject malicious JavaScript code that gets persisted in the database and executed when users view affected pages. The theme fails to properly sanitize user input during web page generation, allowing script execution in the context of other users' browsers.

MitigationUpdate the Create theme to the latest patched version as soon as available. As a temporary measure, implement a WAF rule to filter XSS payloads and review theme code for proper input sanitization and output encoding functions.

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
CreateWordPress extension
Affected:< 2.9.2< 3.5.2

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
High
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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

  1. Identify if Create theme is installed
    Locate the theme directory in your WordPress installation (typically under wp-content/themes/) and confirm the presence of the 'Create' theme by catchthemes. Check for a style.css file with 'Theme Name: Create' or inspect theme headers.
    Affected if The Create theme by catchthemes is present in the theme directory.
  2. Determine the installed version
    Open the style.css file within the Create theme folder and look for the 'Version:' declaration in the theme header comments. Alternatively, access the theme through WordPress admin under Appearance > Themes to view the version displayed.
    Affected if The installed version is less than 2.9.2 or less than 3.5.2.
  3. Identify data input points
    Review the theme for any frontend forms, settings panels, or customization options that accept and store user-provided data (such as custom CSS fields, header/footer scripts, or theme options). Check the theme settings pages in WordPress admin.
    Affected if The theme contains input fields that accept and store user data in the WordPress database.
  4. Inspect stored data for malicious scripts
    Query the WordPress database (wp_options table and any custom postmeta tables) for the theme's stored settings. Search for script tags, javascript: URLs, or event handler attributes (onload, onerror, onclick, etc.) within stored values.
    Affected if Any stored theme settings or custom fields contain unsanitized script tags or JavaScript event handlers.
  5. Review theme code for sanitization gaps
    If you have access to the theme source code, examine the PHP files that handle user input and database storage. Look for instances where $_POST, $_GET, or $_REQUEST data is saved without using sanitization functions like sanitize_text_field, esc_attr, or wp_kses.
    Affected if User input is saved to the database without proper sanitization functions.

You are affected if the Create theme is installed with a version below 2.9.2 or below 3.5.2, and the theme accepts user input that gets stored in the database without proper sanitization.

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 2.9.2 / 3.5.2 or later
Fixed in 2.9.23.5.2
Interim mitigation

Update the Create theme to the latest patched version as soon as available. As a temporary measure, implement a WAF rule to filter XSS payloads and review theme code for proper input sanitization and output encoding functions.

Recommended fix Moderate confidence

Create 2.9.2 (for 2.x branch) or Create 3.5.2 (for 3.x branch)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Dashboard > Appearance > Themes in WordPress admin
  3. 3. Locate the 'Create' theme in your installed themes
  4. 4. Check the current version of the Create theme (theme style.css or theme details)
  5. 5. If using Create version 2.x: Update to version 2.9.2 or later
  6. 6. If using Create version 3.x: Update to version 3.5.2 or later
  7. 7. Update via WordPress: Click 'Update Now' when an update is available, or manually upload the new version from catchthemes.com
  8. 8. After updating, clear any caching plugins and verify the site functions correctly
Caveat Review theme customizer settings and child theme modifications after upgrade as minor CSS/template changes may occur

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

Fix this in Create Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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