CVE-2023-30958
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 security defect was identified in Foundry Frontend that enabled users to potentially conduct DOM XSS attacks if Foundry's CSP were to be bypassed. This defect was resolved with the release of Foundry Frontend 6.225.0.
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 DOM-based cross-site scripting (XSS) vulnerability existed in Foundry Frontend where user-controlled input could be injected into the DOM if Content Security Policy (CSP) protections were bypassed. The vulnerability was addressed in version 6.225.0 through frontend code changes to properly sanitize or escape input handling.
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.225.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 Zabbix Frontend installationLocate the Zabbix web frontend directory on your server. Common paths include /usr/share/zabbix, /var/www/html/zabbix, or check your web server configuration for the document root.Affected if Zabbix Frontend is present on the system
-
Determine installed Zabbix Frontend versionCheck the version file or about page. Look for a VERSION file in the frontend directory, the include/version.php file, or access the Zabbix Frontend About page via the web interface (Administration > General > About).Affected if A version number is returned that is lower than 6.225.0
-
Compare version to affected rangeReview the discovered version number against the affected range: versions prior to 6.225.0 are vulnerable.Affected if The installed version is less than 6.225.0 (for example, 6.224.0, 6.0.0, 5.0.0, etc.)
-
Verify Content Security Policy configurationCheck the Zabbix Frontend configuration file (zabbix.conf.php or similar) for CSP headers, or inspect HTTP response headers from the frontend using browser dev tools or curl -I against the frontend URL.Affected if CSP is disabled, not configured, or contains unsafe directives that could allow inline script execution
A user is affected if Zabbix Frontend version is below 6.225.0 AND the CSP is either misconfigured or can be bypassed, allowing DOM-based XSS injection.
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.225.0
Organizations using affected Foundry versions should upgrade to Foundry Frontend 6.225.0 or later. Since the XSS is contingent on CSP bypass, ensuring CSP is properly configured and not weakened provides defense-in-depth.
6.225.0
- Upgrade Foundry Frontend to version 6.225.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30958 — 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-30958 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