UltraWordPress extension · Themify
CVE-2023-46146
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 · uneditedMissing Authorization 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 confidenceMissing authorization vulnerability in Themify Ultra theme allows unauthorized users to access sensitive functionality that should require proper authentication, with CVSS 8.8 indicating significant potential impact.
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.
-
Verify Themify Ultra theme is installedLog into WordPress admin panel, navigate to Appearance > Themes, and confirm Themify Ultra is installed and activeAffected if Themify Ultra theme is present and active in the WordPress installation
-
Check installed version numberIn WordPress admin, go to Appearance > Themes, click on Themify Ultra theme details, and locate the version number displayedAffected if Version displayed is lower than 7.3.6 (e.g., 7.3.5, 7.3.4, etc.)
-
Confirm WordPress admin accessVerify that the WordPress site has administrator accounts configured and that the themify framework plugin/module is enabledAffected if The Themify framework plugin is active and provides the functionality impacted by the missing authorization
The environment is affected if Themify Ultra theme version is below 7.3.6 and the themify framework functionality is enabled on the WordPress site
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
Update Themify Ultra to version 7.3.6 or later. If an update is unavailable, implement proper authorization checks on all affected functions and restrict access to administrative capabilities.
7.3.6 or later
- Backup your WordPress site before making any changes
- Update Themify Ultra theme to version 7.3.6 or later through WordPress admin > Appearance > Themes > Themify Ultra > Update Now
- Verify the update was successful by checking the theme version in WordPress admin > Appearance > Themes
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ultra
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46146 — 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-46146 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