dbcve.org
Wp Child Theme GeneratorWordPress extension · Wensolutions

CVE-2024-3610

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-21
Fix available
A fix is available. Upgrade to 1.1.2 or later.
See remediation →
62/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 WP Child Theme Generator plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the wctg_easy_child_theme() function in all versions up to, and including, 1.1.1. This makes it possible for unauthenticated attackers to create a blank child theme and activate it cause the site to whitescreen.

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 WP Child Theme Generator plugin for WordPress lacks a capability check on the wctg_easy_child_theme() function, allowing unauthenticated attackers to programmatically create and activate a blank child theme. When a minimal/blank child theme is activated, it causes a fatal error resulting in a WordPress white screen of death, effectively taking the site offline.

MitigationUpdate the plugin to version 1.1.2 or later which includes the capability check; if no patched version is available, disable the plugin and remove it until a fix is released. Maintain site backups before applying any changes.

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
Wp Child Theme GeneratorWordPress extension
Affected:< 1.1.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Locate the WP Child Theme Generator plugin installation
    Check your WordPress wp-content/plugins/ directory for a folder named 'wp-child-theme-generator', 'wp-child-theme-generator-wctg', or similar. If the folder does not exist, the plugin is not installed.
    Affected if the plugin folder exists in wp-content/plugins/
  2. Identify the installed plugin version
    Open the main plugin PHP file in the plugin folder and locate the version comment in the plugin header (e.g., 'Version: x.x.x'), or check the readme.txt file for the 'Stable tag' entry.
    Affected if the version number found is lower than 1.1.2 (for example, 1.1.1, 1.1.0, or any version below 1.1.2)
  3. Confirm the plugin is active on your site
    Log into WordPress admin and navigate to Plugins > Installed Plugins to verify if WP Child Theme Generator is listed as Active, or query the wp_options table for the option_name 'active_plugins' and check if the plugin folder is present in the serialized array.
    Affected if the plugin appears as Active in the WordPress admin or the plugin folder is found in the active_plugins option
  4. Check for unauthorized child theme creation
    Examine your wp-content/themes/ directory for any newly created child theme folders (often named with a prefix like 'wctg-') that you did not create manually. Inspect the style.css file inside to confirm it is a minimal/blank child theme.
    Affected if an unexpected child theme folder exists in the themes directory, especially one with a name pattern suggesting it was created by the plugin

You are affected if the WP Child Theme Generator plugin is installed, active, and the installed version is below 1.1.2, or if unauthorized child themes appear in your themes directory.

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.1.2 or later
Fixed in 1.1.2
Interim mitigation

Update the plugin to version 1.1.2 or later which includes the capability check; if no patched version is available, disable the plugin and remove it until a fix is released. Maintain site backups before applying any changes.

Recommended fix High confidence

1.1.2

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find 'WP Child Theme Generator' in the list
  4. Click 'Update now' if an update is available, or manually update to version 1.1.2
  5. Verify the plugin is running version 1.1.2 after the update
  6. Test child theme generation functionality to ensure it works correctly

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

Fix this in Wp Child Theme Generator 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-3610 — 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-3610 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