CVE-2019-0254
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 Disclosure Management (before version 10.1 Stack 1301) does not sufficiently encode user-controlled inputs, resulting in Cross-Site Scripting (XSS) vulnerability.
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 confidenceSAP Disclosure Management versions prior to 10.1 Stack 1301 contain a Cross-Site Scripting (XSS) vulnerability due to insufficient encoding of user-controlled inputs. Attackers can inject malicious scripts through untrusted input fields that are displayed without proper sanitization.
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< 10.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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.
-
Confirm SAP Disclosure Management installationLocate the SAP Disclosure Management installation directory or check for the application in your SAP software inventory. Common paths include C:\Program Files\SAP\Disclosure Management or /usr/sap/disclosure-management. Check Windows Programs and Features or Linux package managers for the installed package.Affected if SAP Disclosure Management is not found on the system, the system is not affected by this CVE.
-
Identify installed version numberOpen SAP Disclosure Management and navigate to Help > About, or check version files in the installation directory such as version.xml, release.info, or DMVersion.txt. Alternatively, check the SAP Manager transaction or software deployment tools for the installed version.Affected if Unable to determine the version - further investigation required.
-
Compare version against affected rangeCompare your installed version to the affected range: versions prior to 10.1. If your version starts with 10.1, verify it is at least Stack 1301 or higher. Versions 10.1, 10.0, 9.x and below are within the affected range.Affected if Installed version is less than 10.1 (such as 10.0.x, 9.x, or earlier) - the environment is affected by this XSS vulnerability.
-
Identify accessible input fieldsIf running an affected version, log into SAP Disclosure Management and identify user input fields such as document metadata fields, comments, descriptions, or any form inputs where users can enter custom text. These are the potential injection points for XSS.Affected if Input fields that accept freeform text are present and accessible to users - the XSS vulnerability is exploitable in your environment.
Your environment is affected if SAP Disclosure Management version is installed and the version is below 10.1 Stack 1301, with accessible user input fields that lack proper 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.
From vendor data10.1
Upgrade SAP Disclosure Management to version 10.1 Stack 1301 or later to obtain the patched version with proper input encoding.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0254 — 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-2019-0254 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