Symptom

A user who is logged on to the portal and has access to XML Forms in SAP NetWeaver Knowledge Management (KM) sends a preview request for a form. Instead of one of the display transformations configured for the XML Forms project, the request names a different XSL transformation. The server processes it anyway, and the stylesheet's code runs in the context of the portal application.

SAP rates the issue (CVE-2026-109803) with CVSS 9.9. A successful attack can affect the confidentiality, integrity and availability of the application, and because the scope is changed, it can reach beyond KM itself.

For example, an XML Forms project has two display transformations configured: a list view and a detail view.

  • Before the correction: a preview request that names either of the two renders as expected, and a request that names a third, unconfigured stylesheet is processed as well.
  • After the correction: the two configured transformations still render, and the third request is rejected.

The attack usually goes unnoticed. It needs no administrator rights and no interaction from another user, and in the logs it looks like an ordinary preview by an authenticated user. The typical trigger is a user with low privileges, such as a content author, or a compromised account of such a user, who sends a manipulated preview request.

Cause

During XML Forms preview processing, KM accepts the XSL transformation named in the request without checking whether it is configured for the current project. An attacker can therefore choose which stylesheet is processed, and XSL transformations can run code on the server.

Who is affected

All of the following must apply:

  • The system runs one of the affected KMC-CM versions listed below.
  • XML Forms is in use, or at least reachable, in the portal.
  • At least one user who is not fully trusted can open XML Forms functionality or XML Forms project resources.

Affected versions of software component KMC-CM 7.50 (below the patch level that contains the correction):

  • SP031 below patch level 1
  • SP032 below patch level 2
  • SP033 – SP037 below patch level 1
  • any support package below SP031

KMC-CM 7.50 SP038 and later already contain the correction.

To check the version, open SAP NetWeaver Administrator and go to Troubleshooting → Java → System Information → Components, or open http://<HOST>:<PORT>/monitoring/ComponentInfo. Look for the development component of KMC-CM (vendor sap.com) and note its support package and patch level.

To check who can reach XML Forms, review in the portal:

  • which roles contain the XML Forms Builder and the KM iViews that open XML Forms (for example, the Content Management roles), and which users and groups are assigned to them;
  • the permissions on the XML Forms project folders in the KM repository (by default under /etc/xmlforms).

Read the result as follows: you are affected if the KMC-CM patch level is below the fixed level for your support package and users outside a small, trusted group can open XML Forms. A patched system is protected from now on, but the version check does not prove that the issue was not exploited before you patched. See Confirm the result for that.

Prevent the issue on KMC-CM 7.50

At the time of writing, SAP delivers the correction with the patch levels listed above and all later ones. Install the KMC-CM patch for your support package, or move to SP038 or later, with your usual Java deployment process (for example, Software Update Manager).

If you cannot patch right away, restrict XML Forms as a temporary workaround:

  • Remove the XML Forms Builder and the iViews that open XML Forms from all roles except those of trusted users.
  • Review the permissions on the XML Forms project folders and remove write and read access that users do not need for their work.

Keep in mind:

  • The workaround is temporary. SAP strongly recommends installing the correction, either instead of the workaround or after it.
  • The workaround narrows who can attack, but does not close the gap. A trusted user's account can still be misused.
  • Users who lose access cannot create, edit or preview XML Forms content until you restore it. Agree the change with the owners of the affected KM content first.
  • After the correction, existing projects that use explicitly configured display transformations keep working. Custom code, links or bookmarks that pass a transformation that is not configured for the project are rejected. Test such cases on a non-production system before you patch production.
  • To undo the workaround after patching, restore the original role assignments and folder permissions. Document them before you change anything.

On premise, you patch KMC-CM yourself. If SAP operates your portal, for example in SAP S/4HANA Cloud Private Edition or another SAP-managed landscape, check the patch schedule with SAP's cloud operations team instead of changing roles and permissions yourself.

Confirm the result

After patching, check the KMC-CM version again on every portal system, including development, quality and any separate KM or federated portal systems. Each system needs its own patch.

Open a few existing XML Forms and preview them to confirm that the configured display transformations still render correctly.

If you applied the workaround, log on with a test user who should no longer have access and confirm that XML Forms can no longer be opened.

Then review the HTTP access logs and the Java default trace for XML Forms preview requests from users who do not normally work with XML Forms, and for unexpected changes to files on the server. If you find any, treat it as a security incident and contact SAP Support.