CVE-2024-1891
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 · uneditedA stored cross site scripting vulnerability exists in Tenable Security Center where an authenticated, remote attacker could inject HTML code into a web application scan result page.
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 in Tenable Security Center allows authenticated attackers to inject malicious HTML code into web application scan result pages, which then executes in the browsers of other users who view those results.
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< 6.4.0CVSS 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 Tenable Security Center installation and versionLocate the Tenable Security Center installation directory and check the version file or use the command 'sc --version' if available, or check the web interface login page footer for version numberAffected if The installed version is found to be less than 6.4.0 (e.g., 6.3.x, 6.2.x, etc.)
-
Confirm Web Application Scanning is configuredLog into the Tenable Security Center web interface and navigate to Scans > Web Applications to see if any web application scan definitions exist or have been runAffected if Web application scans exist and scan results are viewable in the interface, indicating the vulnerable rendering path is accessible
-
Examine scan result entries for unencoded HTMLReview stored web application scan results directly in the database or via the UI - look for entries where HTML tags (script, img, iframe, onmouseover, etc.) appear unescaped in fields that should display plain textAffected if Scan result fields contain raw HTML or JavaScript that renders as executable code rather than being displayed as text
-
Check browser console for XSS errors or unusual script executionAccess the Tenable Security Center web UI using a browser with developer tools open, navigate to scan result pages, and inspect the console and DOM for any injected scripts executing from scan result fieldsAffected if Arbitrary JavaScript executes or HTML elements render from scan result data that should have been sanitized
You are affected if Tenable Security Center version is below 6.4.0 AND web application scan results are accessible in the interface, regardless of whether exploitation has already occurred.
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 · scoped6.4.0
Implement strict input validation and proper output encoding/escaping on all scan result rendering paths; consider adding Content-Security-Policy headers to mitigate XSS execution.
6.4.0
- Upgrade Tenable Security Center to version 6.4.0 or later to remediate the stored cross-site scripting vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1891 — 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-2024-1891 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