IconsWordPress extension · Themify
CVE-2023-51693
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 Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Themify Icons allows Stored XSS.This issue affects Themify Icons: from n/a through 2.0.1.
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 confidenceA Stored Cross-Site Scripting (XSS) vulnerability exists in Themify Icons versions up to 2.0.1. The vulnerability stems from improper input neutralization during web page generation, allowing attackers to inject malicious scripts that are persistently stored and executed when users view affected pages.
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
IconsWordPress extension
<= 2.0.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 Icons versionLocate the main plugin or theme directory for Themify Icons and inspect the file header (typically in the main PHP file, style.css, or readme.txt) for the version numberAffected if The version listed is 2.0.1 or any version lower than 2.0.1
-
Confirm Themify Icons is actively loadedCheck if the Themify Icons plugin or theme is installed and enabled on the WordPress site by reviewing the active plugins or theme in the wp-admin plugins/themes listAffected if Themify Icons is active and the version cannot be determined or is <= 2.0.1
-
Identify icon rendering functionalityLocate PHP files within the Themify Icons directory that handle icon display or output generation, particularly any files that accept user-supplied data as icon names, classes, or attributesAffected if Icon-related code processes input from user-controllable sources without visible sanitization functions
-
Inspect icon data handlingReview the code paths where icon names or attributes are output to the page, looking for instances where $_GET, $_POST, or database values are directly echoed without encoding functions such as esc_html, esc_attr, or equivalentAffected if User-supplied data flows into page output without proper output encoding
You are affected if Themify Icons version 2.0.1 or lower is installed and actively rendering icon data that originates from user input without sanitization.
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 dataImplement proper output encoding and input validation for all user-supplied data rendered by Themify Icons; update to the latest version if a patch is available.
Fix this in Icons
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51693 — 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-51693 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