CVE-2026-24973
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 NooTheme CitiLights noo-citilights allows Reflected XSS.This issue affects CitiLights: from n/a through <= 3.7.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 confidenceReflected XSS vulnerability in NooTheme CitiLights theme allows attackers to inject malicious scripts through unsanitized user input that gets reflected in web pages. The vulnerability exists in the theme's web page generation logic.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 CitiLights theme is installedLocate the CitiLights theme directory in the CMS (typically under /wp-content/themes/ for WordPress or /themes/ for other CMS platforms). Check for a folder named 'citilights' or similar.Affected if The CitiLights theme folder exists in the system's theme directory.
-
Identify the installed CitiLights versionOpen the theme's main style.css file or a version.php/version.json file within the CitiLights theme folder. Look for a 'Version:' comment or $version variable.Affected if The version cannot be determined or is lower than any available patched version.
-
Locate user input reflection points in theme filesSearch theme PHP files for unsanitized use of superglobal variables ($_GET, $_POST, $_REQUEST, $_COOKIE) that are output to HTML. Look for patterns like echo $_GET['param']; or similar without htmlspecialchars(), esc_html(), or similar sanitization functions.Affected if User-supplied parameters from URL query strings or form submissions are directly echoed to HTML output without sanitization.
-
Identify vulnerable page templatesExamine theme template files (header.php, footer.php, search.php, archive.php, single.php, page.php) for $_REQUEST or $_GET usage in the page body. Check if these values are displayed without escaping.Affected if Template files contain code that reflects URL parameters or form inputs directly into the page content.
-
Test for reflected XSS manuallyUsing a browser or testing tool, visit pages on the site with a test XSS payload in URL parameters (e.g., ?search=<script>alert(1)</script>). Check if the payload appears unescaped in the page response.Affected if The test payload renders as executable JavaScript or appears literally in the page without being HTML-encoded.
The environment is affected if the CitiLights theme is installed and its code reflects URL parameters or form inputs directly into web pages without proper HTML encoding.
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 input validation and output encoding/escaping for all user-supplied data before rendering in HTML context. Update to the latest CitiLights version if available.
- 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-2026-24973 — 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-2026-24973 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