Wp Child Theme GeneratorWordPress extension · Wensolutions
CVE-2023-47873
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in WEN Solutions WP Child Theme Generator.This issue affects WP Child Theme Generator: from n/a through 1.0.9.
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 confidenceThe WP Child Theme Generator plugin versions up to 1.0.9 contains an unrestricted file upload vulnerability allowing attackers to upload files with dangerous types (likely executable PHP files) without proper validation. This could enable remote code execution on the affected WordPress server.
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
< 1.1.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Child Theme Generator plugin is installedLog into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'WP Child Theme Generator' or 'Wensolutions Wp Child Theme Generator' in the listAffected if The plugin appears in the installed plugins list
-
Check installed plugin versionIn the Plugins list, click on the plugin to view its details, or inspect the plugin header in /wp-content/plugins/wp-child-theme-generator/ folder for the Version fieldAffected if The displayed version is less than 1.1.3 (or the version field cannot be verified)
-
Inspect uploaded files directoryCheck the WordPress uploads folder for any recently added PHP files or suspicious files in subdirectories, particularly in /wp-content/uploads/ and /wp-content/themes/ child theme foldersAffected if Unexpected PHP files or executable files exist that were not intentionally uploaded by an administrator
-
Review server access logs for plugin-related upload requestsSearch web server access logs (Apache/nginx) for POST requests to endpoints containing 'child-theme-generator' or 'upload' from the past timeframe, focusing on requests uploading file types like .php, .phtml, or .pharAffected if POST requests to the plugin's upload functionality contain file uploads with dangerous extensions from unexpected IP addresses
If the WP Child Theme Generator plugin is installed with a version below 1.1.3 and the upload functionality is exposed, the environment is likely affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.1.3
Update to the latest version of WP Child Theme Generator (1.0.10 or later) which should include proper file type validation. If immediate updating is not possible, restrict plugin access to trusted administrative users only or disable the plugin until a patch can be applied.
1.1.3
- Upgrade WP Child Theme Generator to version 1.1.3 or later to resolve the unrestricted file upload vulnerability (CWE-434)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Child Theme Generator
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2023-47873 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-47873 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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