CVE-2026-44746
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 a reflected cross-site scripting (XSS) vulnerability in SAP NetWeaver JAVA (JDBC Test Servlet), an unauthenticated attacker could craft a URL that embeds a malicious script. If a victim clicks this link, the injected input is processed during web page generation, resulting in the execution of malicious content in the victim's browser. This could allow the attacker to access and/or modify information related to the webclient, impacting the confidentiality and integrity of the application, with no impact to 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 · high confidenceA reflected cross-site scripting (XSS) vulnerability exists in the JDBC Test Servlet of SAP NetWeaver JAVA. Unauthenticated attackers can craft malicious URLs containing embedded scripts that execute in victims' browsers when clicked, allowing theft of session cookies or manipulation of web content.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 SAP NetWeaver JAVA installation and versionLocate SAP NetWeaver JAVA installation directory and check version files (e.g., in the usr/sap/<SID> directory, look for version manifest files or use SAP LMNG commands like 'dmptool' or SAP MII version info). Compare your installed version against the affected version range provided by SAP security notes.Affected if The installed version falls within the vulnerable version range for this CVE.
-
Locate the JDBC Test ServletIdentify if the JDBC Test Servlet (typically mapped to paths like /JdbcTest or / jdbcTestServlet) is deployed on the SAP NetWeaver JAVA application server. Check the web.xml deployment descriptor in the relevant application or SAP system directory for servlet mappings.Affected if The JDBC Test Servlet is deployed and registered in the application server.
-
Verify if JDBC Test Servlet is enabledCheck the servlet configuration in the SAP NetWeaver JAVA deployment descriptors or SAP Central Configuration Console. Confirm the servlet status is 'enabled' or 'active'.Affected if The JDBC Test Servlet is currently enabled on the system.
-
Check servlet access controlsInspect the security constraints and access control configurations for the JDBC Test Servlet in the web.xml or SAP Internet Transaction Server (ITS) settings. Determine if the servlet allows unauthenticated access.Affected if The JDBC Test Servlet is accessible without authentication (no login required).
You are affected if SAP NetWeaver JAVA is running a vulnerable version AND the JDBC Test Servlet is enabled and accessible to unauthenticated users, allowing reflected XSS execution via crafted URLs.
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 the JDBC Test Servlet or disable the servlet if unused, and implement input validation and output encoding for all user-supplied parameters.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44746 — 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-2026-44746 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