CVE-2022-22531
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 · uneditedThe F0743 Create Single Payment application of SAP S/4HANA - versions 100, 101, 102, 103, 104, 105, 106, does not check uploaded or downloaded files. This allows an attacker with basic user rights to run arbitrary script code, resulting in sensitive information being disclosed or modified.
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 confidenceThe F0743 Create Single Payment application in SAP S/4HANA (versions 100-106) lacks proper validation of uploaded and downloaded files, allowing authenticated users with basic rights to execute arbitrary script code and access or modify sensitive financial data.
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= 100= 101= 102= 103= 104= 105= 106CVSS 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
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Verify SAP S/4HANA versionAccess SAP S/4HANA system information (via SAP transaction SM51 or system overview), and identify the numeric version release (e.g., 100, 101, 102, 103, 104, 105, or 106).Affected if The installed version is 100, 101, 102, 103, 104, 105, or 106.
-
Confirm F0743 application is accessibleCheck if the F0743 transaction (Create Single Payment) is available in the system by attempting to access it via transaction code /n/F0743 or searching for it in the SAP Fiori app catalog under payment processing applications.Affected if The F0743 application is present and accessible in the system.
-
Verify file handling is enabledInspect the F0743 application configuration in transaction SE80 or via SAP Gateway OData service configuration to confirm that file upload and download capabilities for payment files are activated.Affected if File upload or download functionality is enabled for the F0743 application.
-
Check user role assignmentsReview user role assignments using transaction SUIM or PFCG to determine which users have access to the F0743 transaction, particularly users with basic or limited authorization levels.Affected if Users with basic authentication rights have access to the F0743 application.
Your environment is affected if you are running SAP S/4HANA versions 100-106, the F0743 Create Single Payment application is accessible, and users with basic rights can perform file operations within that application.
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 strict file type validation and sanitization for all file operations in the F0743 application, and review SAP S/4HANA security configurations to restrict file handling permissions.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22531 — 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-22531 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