CVE-2018-2474
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 Fiori 1.0 for SAP ERP HCM (Approve Leave Request, version 2) application allows an attacker to trick an authenticated user to send unintended request to the web server. This vulnerability is due to insufficient CSRF protection.
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 confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in SAP Fiori 1.0 for SAP ERP HCM Approve Leave Request version 2. An attacker can craft malicious requests that trick an authenticated user into unknowingly submitting unintended requests to the web server due to insufficient anti-CSRF protections.
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= 1.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 Fiori versionAccess SAP Fiori Admin UI or check system information to verify Fiori version is exactly 1.0Affected if Fiori version is 1.0 and the HCM Approve Leave Request app is deployed
-
Verify HCM Approve Leave Request app is installedCheck the installed Fiori apps in the SAP Fiori Launchpad configuration or app catalog for 'Approve Leave Request' or similar HCM leave management appAffected if The Approve Leave Request application is present and accessible to users
-
Inspect forms for anti-CSRF token presenceLog into Fiori as a user, navigate to the Approve Leave Request feature, and inspect the HTML source or network requests for state-changing forms to check for hidden anti-CSRF token fieldsAffected if Forms lack hidden token fields or tokens are not submitted with requests
-
Check SameSite cookie configurationCapture a session cookie from the Fiori application using browser developer tools or a proxy and inspect the Set-Cookie headers for SameSite attributeAffected if Cookies do not have SameSite=Strict or SameSite=Lax attribute set
-
Verify Origin or Referer header validationSubmit a request to the Approve Leave Request endpoint with a mismatched or missing Origin/Referer header and observe if the server accepts or rejects itAffected if Server accepts requests with missing or mismatched Origin/Referer headers for state-changing operations
A user is affected if they run SAP Fiori version 1.0 with the HCM Approve Leave Request app deployed and the application lacks anti-CSRF tokens in forms, SameSite cookie attributes, and Origin/Referer header validation.
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 anti-CSRF tokens on all state-changing forms and validate them server-side. Additionally, configure SameSite cookie attributes and validate Origin/Referer headers to prevent CSRF attacks.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-2474 — 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-2018-2474 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