CVE-2025-42977
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 NetWeaver Visual Composer contains a Directory Traversal vulnerability caused by insufficient validation of input paths provided by a high-privileged user. This allows an attacker to read or modify arbitrary files, resulting in a high impact on confidentiality and a low impact on integrity.
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 Visual Composer has a directory traversal vulnerability due to insufficient validation of input paths. A high-privileged authenticated attacker can supply specially crafted file paths to read or modify arbitrary files on the host system, leading to high confidentiality impact and low integrity 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/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 SAP NetWeaver Visual Composer installationLocate Visual Composer component in SAP NetWeaver installation. Check for presence of VC (Visual Composer) related modules, services, or WAR files in the SAP NetWeaver directory structure (typically under /usr/sap/<SID>/<instance>/j2ee/ or similar paths depending on installation). Query SAP JVM or SAP Start Service for deployed Visual Composer applications.Affected if Visual Composer component is present in the SAP NetWeaver environment
-
Determine Visual Composer versionCheck the version of the Visual Composer component. This can be found in the SAP NetWeaver Administrator (NWA) under Software Lifecycle Management, or by examining the VC application's manifest/META-INF files. Alternatively, query the SAP system via transaction SM37 or use SAP LMDB.Affected if Version cannot be confirmed as patched or falls within any unpatched version range
-
Verify high-privileged user access existsReview SAP user accounts with high privileges (SAP_ALL, or roles with administrative access to Visual Composer). Check user assignment to roles such as SAP_VC_ADMINISTRATOR or equivalent VC management roles using transaction SUIM or PFCG.Affected if High-privileged authenticated users exist who have access to Visual Composer administration or execution functions
-
Confirm Visual Composer HTTP/HTTPS endpoints are accessibleCheck if Visual Composer is accessible via web browser or API endpoints. Common paths include /VC, /sap/VC, or similar. Verify the SAP ICM (Internet Communication Manager) configuration and whether the VC ports are listening. Use transaction SMICM or check icm/HTTP/... parameters in instance profile.Affected if Visual Composer web interfaces or service endpoints are exposed and reachable
Environment is affected if SAP NetWeaver Visual Composer is installed with an unpatched version and is accessible to high-privileged authenticated users.
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 the relevant SAP security patch when available. Until then, limit high-privileged user access to only necessary personnel, implement strict file system permissions, and monitor for anomalous file access patterns.
- Consultation8.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 $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-42977 — 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-42977 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