CVE-2024-34685
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 · uneditedDue to weak encoding of user-controlled input in SAP NetWeaver Knowledge Management XMLEditor which allows malicious scripts can be executed in the application, potentially leading to a Cross-Site Scripting (XSS) vulnerability. This has no impact on the availability of the application but it has a low impact on its confidentiality and integrity.
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 confidenceCross-Site Scripting (XSS) vulnerability in SAP NetWeaver Knowledge Management XMLEditor due to weak encoding of user-controlled input. Attackers can inject malicious scripts that execute in the application context, impacting user sessions and data integrity.
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.50CVSS 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 SAP NetWeaver Knowledge Management versionCheck the installed version of SAP NetWeaver Knowledge Management And Collaboration (kmc Cm) component in your system. This is typically available via SAP transaction SMICM, SAPLMGEND, or through the SAP Support Portal if you have access to installed software inventory.Affected if The installed version is exactly 7.50 (kmc Cm)
-
Confirm XMLEditor component is deployedVerify whether the XMLEditor component of SAP NetWeaver Knowledge Management is deployed and available in your environment. Check the KM configuration or browse the KM repository structure to locate the XMLEditor functionality.Affected if The XMLEditor component is present and loaded in the KM environment
-
Check if XMLEditor is accessible to usersDetermine whether the XMLEditor functionality is exposed to end users through any KM portals, Web Dynpro applications, or KM iViews. Review the UME roles and KM permission assignments for the XMLEditor.Affected if The XMLEditor is accessible to authenticated or anonymous users
-
Verify user input handling in XMLEditorInspect how the XMLEditor processes user-supplied XML content. Determine if user-provided data within the editor is rendered or previewed without output encoding.Affected if The XMLEditor renders user-supplied XML content without proper context-aware encoding
You are affected if you run version 7.50 of SAP NetWeaver Knowledge Management And Collaboration (kmc Cm) with the XMLEditor component deployed and accessible to users who can input XML 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 dataImplement proper output encoding and input validation for all user-supplied data in the XMLEditor component; apply context-appropriate sanitization and consider Content Security Policy headers to mitigate script injection.
- 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-34685 — 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-34685 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