UltraWordPress extension · Themify
CVE-2023-46149
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 Themify Themify Ultra.This issue affects Themify Ultra: from n/a through 7.3.5.
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 confidenceUnrestricted file upload vulnerability in Themify Ultra WordPress theme allows attackers to upload dangerous file types (e.g., malicious scripts) without proper validation, potentially achieving remote code execution on the 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
UltraWordPress extension
<= 7.3.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm Themify Ultra theme is installedCheck the WordPress themes directory (wp-content/themes/) for the themify-ultra folder. Look for style.css in that folder and review the theme header comment for 'Theme Name: Themify Ultra'.Affected if Themify Ultra theme folder exists in the WordPress themes directory
-
Identify installed theme versionOpen the style.css file in wp-content/themes/themify-ultra/ and locate the 'Version:' field in the theme header comment. Compare this version number to 7.3.5.Affected if The version number is 7.3.5 or lower
-
Check for exposed file upload functionalityReview the Themify Ultra theme settings and builder components for any file upload features that may be accessible to unauthenticated or low-privilege users. Check for custom upload endpoints or builder elements that handle file uploads.Affected if File upload functionality is enabled and accessible through the theme or its builder
-
Audit upload directories for dangerous file typesSearch upload directories (typically wp-content/uploads/) for executable file extensions such as .php, .phtml, .js, .svg, or .exe that were uploaded outside expected workflows.Affected if Unexpected executable files are present in upload directories
The environment is affected if Themify Ultra theme version 7.3.5 or lower is installed AND file upload functionality through the theme is exposed and accessible.
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.
From vendor dataUpdate Themify Ultra to version 7.3.6 or later. If immediate update is not possible, disable file upload functionality or implement server-side validation to restrict allowed file types and prevent execution in upload directories.
Fix this in Ultra
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46149 — 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-46149 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