CVE-2024-12211
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 8.1 to Infinity 24.2.0 are affected by an Stored XSS issue with profile.
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 8.1 through Infinity 24.2.0 contain a stored cross-site scripting (XSS) vulnerability in the profile functionality. Attackers can inject malicious JavaScript payloads into profile fields that persist on the server and execute when other users view the affected profile, potentially leading to session hijacking or credential theft.
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>= 8.1, < 23.1.4>= 24.1.0, < 24.1.2= 24.2.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Determine installed Pega Platform versionAccess the Pega Administration console (Designer Studio) and navigate to System > Release or check the 'About Pega' page typically found in the system diagnostic settings. Alternatively, check the prpcUtils or management scripts if available in your deployment.Affected if The installed version falls within one of these ranges: >= 8.1 and < 23.1.4; >= 24.1.0 and < 24.1.2; or exactly 24.2.0
-
Verify profile functionality is in useConfirm that the Pega Platform profile management features are enabled and accessible to users. Check if user profiles (including operator profiles) can be accessed and edited through the Pega UI or Pega API.Affected if Profile functionality is enabled and users can create or edit their profile information
-
Inspect profile field content for malicious payloadsQuery the Pega database tables that store operator profile data (typically tables related to pyOperator or similar operator-related data classes). Look for suspicious script tags, javascript: URIs, or HTML event handlers in profile-related fields.Affected if Any profile fields contain unsanitized script tags, event handlers, or other XSS payloads that were not properly encoded on output
-
Review profile access logs for XSS attemptsExamine Pega Platform access logs and audit trails for unusual patterns in profile field submissions. Look for requests to profile update endpoints containing characters typical of XSS payloads such as <script, onerror, onload, or javascript:.Affected if Logs show profile update requests containing XSS payload patterns that may have been successfully stored
A defender is affected if they are running any Pega Platform version between 8.1 and 23.1.3, between 24.1.0 and 24.1.1, or exactly version 24.2.0, with profile functionality enabled and potentially exploitable stored XSS payloads present in profile data.
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 · scoped23.1.424.1.2
Upgrade Pega Platform to the latest version or apply the vendor-provided patch. Implement input validation and output encoding for all profile-related user inputs, and configure Content Security Policy headers to mitigate XSS execution.
23.1.4 or later (for 8.1+ to 23.1.3); 24.1.2 or later (for 24.1.0-24.1.1); contact Pega Support for 24.2.0 patch
- 1. Identify the current Pega Platform version by checking the system banner or about Pega section
- 2. If running version >= 8.1 and < 23.1.4: Plan upgrade to version 23.1.4 or later
- 3. If running version >= 24.1.0 and < 24.1.2: Plan upgrade to version 24.1.2 or later
- 4. If running version 24.2.0: Contact Pega Support (support.pega.com) to confirm the patched version for this release
- 5. Before upgrading in production, test the new version in a staging environment to verify compatibility with custom rules and integrations
- 6. Perform a full backup of the Pega database and rules repository before applying the upgrade
- 7. Apply the upgrade following Pega's standard upgrade documentation
- 8. After upgrade, verify that the profile functionality works correctly and the XSS vulnerability is resolved
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-2024-12211 — 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-2024-12211 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