CVE-2023-26292
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 Forcepoint Cloud Security Gateway (CSG) Portal on Web Cloud Security Gateway, Email Security Cloud (login_submit.mhtml modules), Forcepoint Web Security Portal on Hybrid (login_submit.mhtml modules) allows Reflected XSS.This issue affects Cloud Security Gateway (CSG): before 03/29/2023; Web Security: before 03/29/2023.
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 · high confidenceReflected XSS vulnerability in Forcepoint Cloud Security Gateway and Web Security Portal login modules (login_submit.mhtml). User-supplied input in the login form is insufficiently sanitized and reflected in the HTTP response without proper encoding, allowing injection of malicious JavaScript code that executes in the victim's browser.
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< 2023-03-29< 2023-03-29CVSS 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 deployed Forcepoint productDetermine whether Forcepoint Cloud Security Gateway or Forcepoint Web Security is installed in your environment. Check installed software inventory, running services, or network devices for these products.Affected if Neither product is deployed, then not affected.
-
Check product version against affected rangeLocate the installed version of Forcepoint Cloud Security Gateway or Forcepoint Web Security. Compare the version or build date to the threshold date 2023-03-29.Affected if Version is earlier than 2023-03-29 or build date predates March 29, 2023.
-
Verify login_submit.mhtml module is accessibleConfirm the login portal is exposed by accessing the login_submit.mhtml endpoint on your Forcepoint gateway or web security portal. This is typically found at the login page URL path.Affected if The login module is accessible and returns HTTP response.
-
Test for reflected input in login parametersSubmit a test string such as <script>alert('test')</script> in the login username or password field and inspect the HTTP response to see if the payload is reflected unencoded.Affected if The submitted test string appears in the response without HTML encoding (e.g., raw <script> tags visible in response body).
You are affected if Forcepoint Cloud Security Gateway or Web Security is deployed with a version or build date earlier than 2023-03-29 AND the login_submit.mhtml module reflects unsanitized 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 · scoped2023-03-29
Apply Forcepoint security updates released on or after 03/29/2023 to Cloud Security Gateway and Web Security products. Validate that the login_submit.mhtml modules properly encode output before rendering.
Any version of Forcepoint Cloud Security Gateway or Web Security released on or after 2023-03-29
- Log in to the Forcepoint support portal at support.forcepoint.com
- Navigate to the product downloads or patches section for Cloud Security Gateway (CSG) and/or Web Security
- Locate and download the version released on or after March 29, 2023
- Follow Forcepoint's standard upgrade documentation to apply the update to your deployment
- After upgrade, verify that the login_submit.mhtml modules are updated and the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26292 — 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-26292 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