CVE-2023-26465
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 · uneditedPega Platform versions 7.2 to 8.8.1 are affected by an XSS issue.
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 confidencePega Platform versions 7.2 through 8.8.1 contain a cross-site scripting (XSS) vulnerability that allows attackers to inject malicious scripts into web pages viewed by other users. The medium severity (CVSS 6.1) indicates user interaction is required, such as clicking a crafted link or viewing malicious content.
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>= 7.2, <= 8.8.1CVSS 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 installed Pega Platform versionLog into Pega Designer Studio or Pega Management Console and navigate to System > Release or System > Settings > Version. Alternatively, check the startup logs or the prbootstrap.properties/prconfig.xml files in the Pega installation directory for the 'pega.version' or similar version property.Affected if The displayed version number is between 7.2 and 8.8.1 inclusive, indicating the installation falls within the vulnerable version range.
-
Confirm web client access is enabledVerify that the Pega web tier or web-based interfaces are accessible. Check the Pega application server configuration and confirm that the prweb or appropriate web endpoints are exposed and operational.Affected if Web interfaces are accessible, because XSS exploitation requires users to view malicious content through the web browser.
-
Check for custom activity or script exposureReview the Pega rulebase for exposed activities, controls, or HTML fragments that handle user input without output encoding. Look in the Rule-Obj-Activity and Rule-HTML-File rule types for any unencoded 'pega:ref' or similar parameters.Affected if User-supplied input can be rendered in HTML responses without proper encoding, making the reflected XSS exploitable.
-
Identify if external users have accessReview access groups and authentication configurations in Pega to determine if unauthenticated or external users can access the system through web portals, Customer Service portals, or Pega Express interfaces.Affected if External or unauthenticated users can access Pega web portals, as they could click malicious links or encounter injected scripts.
A user is affected if their Pega Platform installation version is 7.2 through 8.8.1 and the web interfaces are accessible to users who could click crafted links or view malicious content.
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.
From vendor dataUpgrade Pega Platform to the vendor-patched version (8.8.2 or later). If immediate patching is not feasible, implement output encoding and input validation on affected endpoints, and configure Content Security Policy headers to mitigate XSS execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26465 — 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-26465 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