dbcve.org
Cloud Security GatewayApplication · Forcepoint

CVE-2023-26290

MEDIUM · 6.1 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 2023-03-29 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Improper 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_reset_request.mhtml modules), Forcepoint Web Security Portal on Hybrid (login_reset_request.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 confidence

Reflected XSS vulnerability in Forcepoint login_reset_request.mhtml modules across Cloud Security Gateway Portal, Email Security Cloud, and Web Security Portal. Unsanitized user input is reflected back in web pages, allowing attackers to inject malicious scripts that execute in victim browsers.

MitigationApply vendor patch released on 03/29/2023 or later to all affected Forcepoint products. If patching is not immediately possible, implement WAF rules to filter malicious input in login_reset_request.mhtml endpoints.

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
Cloud Security GatewayApplication
Affected:< 2023-03-29
Web SecurityApplication
Affected:< 2023-03-29

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Forcepoint product
    Access the administrative console or check installed packages to determine which Forcepoint product is deployed: Cloud Security Gateway Portal, Email Security Cloud, or Web Security Portal.
    Affected if Any of these three products is installed without knowing the version
  2. Determine the product version
    Locate the version information in the product admin panel, About section, or system information page. Compare the build/date to the patch release date of 2023-03-29.
    Affected if The installed version is dated before 2023-03-29 or the version number is lower than the patched release
  3. Verify the vulnerable endpoint exists
    Attempt to access the login_reset_request.mhtml endpoint by navigating to the portal login page and inspecting available reset request URLs or checking if the .mhtml extension is served by the web server.
    Affected if The login_reset_request.mhtml endpoint is accessible and responds to requests
  4. Test for reflected input in password reset flow
    Submit a test string with identifiable characters (such as XSSTEST123) as part of a password reset request and examine if the same string appears unescaped in the response page source.
    Affected if User-supplied input is reflected verbatim in the HTML response without encoding or sanitization

A user is affected if they are running any Forcepoint Cloud Security Gateway or Web Security version dated before March 29, 2023, and the login_reset_request.mhtml endpoint reflects input without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2023-03-29 or later
Fixed in 2023-03-29
Interim mitigation

Apply vendor patch released on 03/29/2023 or later to all affected Forcepoint products. If patching is not immediately possible, implement WAF rules to filter malicious input in login_reset_request.mhtml endpoints.

Recommended fix High confidence

Forcepoint Cloud Security Gateway and Web Security version 2023-03-29 or later

  1. Upgrade Forcepoint Cloud Security Gateway to version 2023-03-29 or later
  2. Upgrade Forcepoint Web Security to version 2023-03-29 or later
  3. After upgrading, verify the login_reset_request.mhtml module is no longer vulnerable to reflected XSS by confirming the fix in release notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Security Gateway Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-26290 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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