UltraWordPress extension · Themify
CVE-2023-46147
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 · uneditedDeserialization of Untrusted Data 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 confidenceThis is a deserialization vulnerability in the Themify Ultra WordPress theme. PHP deserialization flaws occur when untrusted data is passed to unsafe unserialize() functions, potentially allowing attackers to execute arbitrary code or perform other attacks. The CVSS 8.8 indicates high severity with likely remote code execution capability.
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.6CVSS 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.
-
Identify Themify Ultra versionCheck the theme version in WordPress admin under Appearance > Themes, or inspect the style.css file in wp-content/themes/themify-ultra/ and look for the 'Version:' headerAffected if The version listed is below 7.3.6 (for example, 7.3.5, 7.3.0, etc.)
-
Confirm theme is activeIn WordPress admin, verify that Themify Ultra is the currently active themeAffected if Themify Ultra is the active theme on the WordPress site
-
Check for unsafe deserialization codeSearch the themify-ultra theme files for occurrences of unserialize() being called on request parameters (such as $_GET, $_POST, or $_REQUEST) without prior sanitizationAffected if Files contain unserialize() calls directly on user-supplied input without validation
-
Identify data flow to deserializationReview theme files that handle form submissions, AJAX requests, or URL parameters and trace whether those inputs reach unserialize() functionsAffected if User-supplied data from HTTP requests flows into unserialize() without validation
If the installed Themify Ultra version is below 7.3.6, the theme is active, and unsafe unserialize() calls exist on user input, the environment is vulnerable to CVE-2023-46147.
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 · scoped7.3.6
Replace unsafe PHP deserialization (unserialize()) with safe alternatives like json_decode() and implement strict input validation. Ensure all user-supplied data is validated before deserialization.
Themify Ultra version 7.3.6
- Log in to the WordPress admin dashboard
- Navigate to Appearance > Themes
- Locate the Themify Ultra theme
- Click on the theme and select Update to version 7.3.6 or later, or use the WordPress theme update mechanism to update Themify Ultra to the latest version
- After updating, verify the theme version is 7.3.6 or higher in Themes > Themify Ultra > Theme Details
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ultra
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46147 — 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-46147 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