CVE-2025-27428
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 directory traversal vulnerability, an authorized attacker could gain access to some critical information by using RFC enabled function module. Upon successful exploitation, they could read files from any managed system connected to SAP Solution Manager, leading to high impact on confidentiality. There is no impact on integrity or availability.
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 confidenceA directory traversal vulnerability in SAP Solution Manager allows authenticated attackers to read arbitrary files from any managed system connected to the Solution Manager via RFC-enabled function modules, resulting in high confidentiality impact.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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 Solution Manager installationCheck for SAP Solution Manager processes or web interfaces. Look for SMDA (Solution Manager Diagnostic Agent) processes, or access the Solution Manager web portal (typically ports 50000-50010 or custom ports). Use transaction SM_WORKCENTER or check system information via SAP GUI.Affected if SAP Solution Manager is installed and running in the environment
-
Determine Solution Manager versionIn SAP GUI, use transaction SM37 to view system version info, or use SAP MII version check. Query the SAP system table VERSION or check the SAP note 2408073 for version details. Compare your installed version against SAP security notes addressing CVE-2025-27428.Affected if The installed version matches the vulnerable version range for CVE-2025-27428 (consult SAP security notes for specific version numbers)
-
Verify RFC-enabled function modules are accessibleUse transaction SM59 to view RFC destinations. Check if RFC function modules related to file operations (such as EPS_GET_FILE_LIST, or file transfer functions) are exposed. Use transaction SE37 to inspect function module AUTHORITY_CHECK_RFC.Affected if RFC function modules capable of file system access are enabled and accessible to the attacker
-
Check RFC authorization settingsUse transaction SUIM to check RFC authorizations for user roles. Examine if users have RFC access to function modules that allow file operations. Review roles with S_RFC authorization object.Affected if Users (especially low-privilege or external users) have RFC authorization to vulnerable function modules without proper restrictions
-
Confirm directory traversal attack surfaceTest if function module parameters accept path traversal sequences (.. or absolute paths). Use transaction SE37 to invoke suspected function modules with paths like ../../etc/passwd or absolute file paths to confirm vulnerability.Affected if RFC-enabled function modules accept and process path traversal sequences without proper validation
The environment is affected if SAP Solution Manager is running with vulnerable RFC-enabled function modules that allow unauthenticated or low-privilege users to perform file system operations via path traversal.
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 dataApply SAP security patches for CVE-2025-27428 and review/restrict RFC-enabled function module access to prevent unauthorized file system traversal.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27428 — 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-2025-27428 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