CVE-2024-47594
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 · uneditedSAP NetWeaver Enterprise Portal (KMC) does not sufficiently encode user-controlled inputs, resulting in Cross-Site Scripting vulnerability in KMC servlet. An attacker could craft a script and trick the user into clicking it. When a victim who is registered on the portal clicks on such link, confidentiality and integrity of their web browser session could be compromised.
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 confidenceThis is a reflected Cross-Site Scripting (XSS) vulnerability in SAP NetWeaver Enterprise Portal's Knowledge Management Component (KMC) servlet. The application fails to properly encode user-controlled inputs, allowing attackers to inject malicious JavaScript code via crafted URLs that execute in the context of authenticated users' browser sessions when clicked.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 Enterprise Portal installationCheck the SAP system information via transaction code SM37 or examine the SAP system landscape directory (SLD) for the installed product and version. Alternatively, check the SAP system overview screen during logon for the release version.Affected if The installed product is SAP NetWeaver Enterprise Portal and the version is exactly 7.50
-
Verify Knowledge Management Component (KMC) is activeAccess the SAP Enterprise Portal and navigate to System Administration > System Configuration > Knowledge Management. Verify the KMC service is deployed and running. Alternatively, attempt to access a KMC servlet URL path such as /kmc or /irj/portal under the Enterprise Portal context.Affected if The KMC servlet is deployed and accessible in the SAP Enterprise Portal environment
-
Confirm user input reflection in KMC servlet URLsReview the KMC servlet configuration and identify any URL parameters that accept user input. Test by accessing a KMC URL with a test parameter value (for example, appending ?testparam=testvalue to a known KMC endpoint) and inspect if the parameter value is reflected in the response without encoding.Affected if URL parameters passed to KMC servlet are reflected in the HTML response without proper encoding or sanitization
-
Check authentication requirementsVerify that exploitation requires an authenticated user session by attempting to access the KMC servlet URL with and without valid SAP Enterprise Portal credentials.Affected if The vulnerable endpoint is accessible to authenticated users, meaning a user with valid credentials could be tricked into clicking a malicious URL
The environment is affected if SAP NetWeaver Enterprise Portal version 7.50 is running with the Knowledge Management Component servlet accessible to authenticated users, and user-supplied URL parameters are reflected in responses without output encoding.
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 · scopedApply output encoding to all user inputs in the KMC servlet and implement input validation. Monitor for SAP security notes and apply patches when available. Users should avoid clicking untrusted links until the patch is applied.
- Check SAP Security Notes for CVE-2024-47594 to obtain the relevant patch
- Apply the patch via SAP Support Portal after reviewing the SAP Note details
- Verify the fix by testing the KMC servlet with the previously identified attack vector
- Ensure all portal administrators are informed of the security update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47594 — 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-47594 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