CVE-2026-23973
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 uxper Golo golo allows Reflected XSS.This issue affects Golo: from n/a through < 1.7.5.
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 uxper Golo allows attackers to inject malicious scripts through user input that is improperly neutralized during web page generation. The vulnerability exists in versions prior to 1.7.5.
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.
-
Locate Golo installationIdentify the server or environment where uxper Golo is deployed. This may be a web server, application server, or container hosting the Golo application.Affected if Golo software is present in the environment
-
Identify Golo versionCheck the installed version of Golo. This is typically found in the application metadata, about page, or version file within the Golo installation directory. Consult the product documentation for the specific method to retrieve the version number.Affected if Unable to determine the version or version is below 1.7.5
-
Compare against affected rangeCompare the identified version to the affected range: versions prior to 1.7.5. If the version is 1.7.5 or higher, the vulnerability is patched.Affected if Installed version is lower than 1.7.5
-
Verify web accessConfirm that the Golo web interface is accessible to users or external attackers, as reflected XSS requires the application to process and reflect user input in web pages.Affected if Web interface is exposed and version is below 1.7.5
The environment is affected if uxper Golo is running and the installed version is lower than 1.7.5, with the web interface accessible to process user input.
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 · scopedUpgrade to Golo version 1.7.5 or later which contains the patch for this vulnerability. Additionally, implement proper input validation and output encoding on all user-supplied data before rendering in web pages.
1.7.5 or later
- Identify the current version of the uxper Golo plugin/theme installed on the site
- Create a full backup of the website before proceeding with any updates
- Update the Golo plugin to version 1.7.5 or later to resolve the reflected XSS vulnerability
- After updating, verify the fix by testing the previously vulnerable input fields for XSS vulnerability
- Ensure all other plugins and themes are also kept up to date
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23973 — 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-23973 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