dbcve.org
Business Server PagesApplication · Sap

CVE-2026-24328

MEDIUM · 6.1 CVSS v3.1 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
SAP TAF_APPLAUNCHER within Business Server Pages allows unauthenticated attacker to craft malicious links that, when clicked by a victim, redirect them to attacker?controlled sites, potentially exposing or altering sensitive information in the victim�s browser. This results in a low impact on confidentiality and integrity, with no impact on the availability of the application.

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 confidence

This is an open redirect vulnerability in SAP TAF_APPLAUNCHER within Business Server Pages. An unauthenticated attacker can craft malicious links containing attacker-controlled URLs that, when clicked by a victim, redirect them from the legitimate SAP site to a malicious site. This enables phishing attacks and potential credential theft by exploiting the trusted reputation of the SAP domain.

MitigationApply the relevant SAP security patch for TAF_APPLAUNCHER. As a compensating control, implement URL validation or allowlist filtering for redirect parameters and configure Content Security Policy (CSP) headers to restrict redirect destinations.

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
Business Server PagesApplication
Affected:= 740= 758= 2008_1_700= 2008_1_710

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Business Server Pages installation
    Identify if SAP Business Server Pages (BSP) is installed in your SAP environment. Check via SAP transaction code BSP41 or review system component information via transaction SM37, SM50, or SAP MMC snap-in for the BSP runtime components.
    Affected if Business Server Pages runtime is present and active in the environment
  2. Check BSP version against affected releases
    Retrieve the installed Business Server Pages version via SAP transaction code SPAM (Support Package Manager), or check the SAP system info via transaction SM37 and compare the BSP version to the affected versions: 740, 758, 2008_1_700, 2008_1_710.
    Affected if The installed BSP version exactly matches one of the affected versions: 740, 758, 2008_1_700, or 2008_1_710
  3. Verify TAF_APPLAUNCHER is accessible
    Check if the TAF_APPLAUNCHER application component is deployed and accessible in the SAP system. This can be verified by attempting to access the BSP application path /sap/bc/bsp/sap/taf_applauncher or reviewing BSP application metadata via transaction SE80.
    Affected if TAF_APPLAUNCHER BSP application is deployed and publicly or internally accessible
  4. Inspect for redirect parameters in TAF_APPLAUNCHER
    Review the TAF_APPLAUNCHER application code (via transaction SE80) or monitor HTTP requests for redirect-related parameters (such as url, redirect, target, or similar) that accept user-controlled URLs and could be exploited for open redirect.
    Affected if TAF_APPLAUNCHER accepts redirect parameters without strict validation or allowlisting

Your environment is affected if Business Server Pages version 740, 758, 2008_1_700, or 2008_1_710 is installed AND the TAF_APPLAUNCHER application is accessible and processes redirect parameters without validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patch for TAF_APPLAUNCHER. As a compensating control, implement URL validation or allowlist filtering for redirect parameters and configure Content Security Policy (CSP) headers to restrict redirect destinations.

Fix this in Business Server Pages Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24328 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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