CVE-2022-26102
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 missing authorization check, SAP NetWeaver Application Server for ABAP - versions 700, 701, 702, 731, allows an authenticated attacker, to access content on the start screen of any transaction that is available with in the same SAP system even if he/she isn't authorized for that transaction. A successful exploitation could expose information and in worst case manipulate data before the start screen is executed, resulting in limited impact on confidentiality and integrity of the application.
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 confidenceSAP NetWeaver ABAP application server lacks proper authorization checks before rendering transaction start screens, allowing any authenticated user to access transaction content they aren't authorized to execute. This broken access control enables information disclosure and potential data manipulation at the start screen before transaction execution completes.
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= 700= 701= 702= 731CVSS 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.
-
Identify installed SAP NetWeaver ABAP versionExecute transaction code SM51 or check the SAP system version via SAP GUI: Log in to the ABAP system, enter transaction SM51, and note the Release and Kernel version displayed. Alternatively, use transaction SWI1 or check system profile parameters.Affected if The installed version matches 700, 701, 702, or 731 exactly (these are the only affected versions listed).
-
Review transaction code authorization objectsUse transaction SUIM (User Information System) or directly query authorization objects. Check if the S_TCODE object is properly configured with restrictive values for non-privileged users.Affected if Users have access to transaction codes they should not have permission to execute, indicating S_TCODE restrictions are not enforced.
-
Test unauthorized transaction access at start screenAs a low-privileged authenticated user, attempt to call a transaction they are not authorized for (e.g., via URL parameter /n/ transaction code, or by attempting to start the transaction). Observe whether the transaction start screen renders before an authorization check error occurs.Affected if The transaction start screen loads and displays content before any authorization check error is thrown, meaning the vulnerability is present.
-
Verify authority-check implementation in custom transactionsReview ABAP code for transactions that call authority-check or S_TCODE validation only after the initial screen has rendered. Use transaction SE93 to review transaction properties, or use transaction SLIN for extended program checks.Affected if Transactions lack proper authority-check calls before screen rendering, or authorization errors occur only after transaction execution rather than at start screen.
A system is affected if it runs SAP NetWeaver ABAP versions 700, 701, 702, or 731 AND low-privileged authenticated users can view transaction start screens for unauthorized transactions before authorization checks block execution.
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 and enforce authorization checks (e.g., S_TCODE, authority-check) before displaying transaction start screens; apply SAP security patches if available.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26102 — 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-2022-26102 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