CVE-2023-32244
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 · uneditedImproper Privilege Management vulnerability in xtemos Woodmart Core allows Privilege Escalation.This issue affects Woodmart Core: from n/a through 1.0.36.
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 · low confidenceImproper Privilege Management vulnerability in xtemos Woodmart Core (a WordPress theme) allows authenticated users to escalate their privileges to administrative levels. The specific mechanism is not detailed in available references, but the vulnerability affects versions up to and including 1.0.36.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Locate Woodmart Core installationCheck your WordPress installation for the xtemos Woodmart theme or plugin. Common paths: wp-content/themes/woodmart/ or wp-content/plugins/woodmart-core/. Verify the presence of the xtemos Woodmart Core component.Affected if Woodmart Core is not found in the WordPress installation, the user is not affected by this vulnerability.
-
Identify the installed versionOpen the main version file: for themes check wp-content/themes/woodmart/style.css header for 'Version:' line; for plugins check wp-content/plugins/woodmart-core/woodmart-core.php for version definition. Note the exact version number displayed.Affected if The version cannot be determined, assume potential exposure and treat as affected.
-
Compare version against affected rangeCompare your identified version number to the affected range: versions 1.0.36 and below are vulnerable. For example: 1.0.36 = affected, 1.0.35 = affected, 1.0.37 = not affected, 1.0.37.1 = not affected.Affected if Your installed version is 1.0.36 or lower, the environment is affected by this privilege escalation vulnerability.
-
Verify user account configurationReview WordPress user roles in the wp-users database table or via Users > All Users in the admin dashboard. Check if any non-administrator user accounts exist that could potentially exploit this privilege escalation flaw.Affected if Multiple user roles exist beyond administrator, and Woodmart Core version is 1.0.36 or lower, the vulnerability is exploitable in your environment.
Your environment is affected if xtemos Woodmart Core is installed with version 1.0.36 or lower and your WordPress site has user accounts with privileges below administrator level.
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 Woodmart Core to a version newer than 1.0.36; if no patched version is available, consider disabling the plugin or restricting administrative access until a fix is released.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32244 — 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-32244 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