dbcve.org
Child Theme CreatorWordPress extension · Orbisius

CVE-2024-43276

MEDIUM · 6.1 CVSS v3.1 Published 2024-08-18
Fix available
A fix is available. Upgrade to 1.5.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 (XSS or 'Cross-site Scripting') vulnerability in Svetoslav Marinov (Slavi) Child Theme Creator allows Reflected XSS.This issue affects Child Theme Creator: from n/a through 1.5.4.

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

Reflected XSS vulnerability in the Child Theme Creator WordPress plugin allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in web pages without proper encoding.

MitigationApply proper input sanitization and output encoding/escaping for all user-supplied data before rendering in HTML context. Update to patched version if available or implement WAF rules as temporary measure.

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
Child Theme CreatorWordPress extension
Affected:< 1.5.5

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 plugin is installed
    Navigate to WordPress Admin > Plugins and locate 'Orbisius Child Theme Creator' in the list of installed plugins
    Affected if Plugin appears in the installed plugins list
  2. Check plugin activation status
    In the Plugins list, verify whether Orbisius Child Theme Creator is currently activated (status shows 'Active' underneath the plugin name)
    Affected if Plugin status is Active
  3. Determine installed version
    In the Plugins list, click on the plugin name to view details, or check the plugin's readme.txt file in /wp-content/plugins/ folder for the 'Version' field in the plugin header
    Affected if Version number is lower than 1.5.5 (for example: 1.5.4, 1.5.3, 1.0.0, etc.)
  4. Identify user input reflection points
    Access the plugin settings pages (Child Theme Creator options page in WordPress admin) and look for form fields, URL parameters, or any input areas where data is echoed back to the user without visible encoding
    Affected if User-supplied values from forms or URL parameters are reflected in the page output without HTML encoding
  5. Verify lack of output encoding
    Examine the plugin's main PHP file for functions that output user input (search for echo, print, printf, or similar) without using escaping functions like esc_html(), esc_attr(), or esc_url() on user-controlled variables
    Affected if User input variables are output directly without escaping functions

User is affected if the Orbisius Child Theme Creator plugin is active with a version lower than 1.5.5 and contains pages where user input is reflected without HTML encoding.

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.5.5 or later
Fixed in 1.5.5
Interim mitigation

Apply proper input sanitization and output encoding/escaping for all user-supplied data before rendering in HTML context. Update to patched version if available or implement WAF rules as temporary measure.

Recommended fix High confidence

Child Theme Creator version 1.5.5

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find 'Child Theme Creator' plugin
  4. Click 'Update Now' to update to version 1.5.5 or later
  5. Verify the update was successful by checking the plugin version

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

Fix this in Child Theme Creator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

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