VulnerabilityPublished 10 Feb 2026

CVE-2026-24328: SAP_SE Business Server Pages Application (TAF_APPLAUNCHER) · URL Redirection to Untrusted Site

Affects SAP_SE Business Server Pages Application (TAF_APPLAUNCHER)Source CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SAP_SEBusiness Server Pages Application (TAF_APPLAUNCHER)	Affected =2008_1_710 =740 =758	Fixed in–

AI-suggested

European organizations should immediately verify if they are running affected versions of SAP ST-PI components (2008_1_700, 2008_1_710, 740, 758) and prioritize upgrading to patched versions once available. In the interim, implement strict URL validation and sanitization controls within SAP Business Server Pages to prevent open redirects. Deploy web application firewalls (WAFs) with rules to detect and block suspicious redirect patterns. Conduct targeted user awareness training focusing on phishing risks associated with suspicious links, emphasizing verification of URLs before clicking. Monitor logs for unusual redirect activity and implement browser security policies such as Content Security Policy (CSP) to restrict navigation to trusted domains. Consider disabling or restricting the use of the TAF_APPLAUNCHER component if not essential. Collaborate with SAP support for any vendor-specific mitigations or patches. Regularly review and update incident response plans to include scenarios involving open redirect exploitation.

Description

CVE-2026-24328 is a medium-severity vulnerability in the SAP Business Server Pages Application (TAF_APPLAUNCHER) that allows unauthenticated attackers to craft malicious URLs causing victims to be redirected to attacker-controlled sites. This URL redirection flaw (CWE-601) requires user interaction (clicking the link) and can lead to limited confidentiality and integrity impacts by exposing or altering sensitive information in the victim's browser context. There is no impact on application availability. The vulnerability affects specific versions of SAP ST-PI components and has a CVSS score of 6.1. No known exploits are currently reported in the wild. European organizations using affected SAP versions should prioritize patching and implement strict URL validation and user awareness to mitigate risks. Countries with significant SAP enterprise deployments and critical infrastructure relying on SAP are most likely to be impacted.

Impact

For European organizations, this vulnerability poses a moderate risk primarily through social engineering and phishing attacks that leverage the open redirect to attacker-controlled sites. Confidentiality could be compromised if sensitive session information or credentials are exposed during redirection. Integrity risks arise if attackers manipulate the victim's browser context or inject malicious content via the redirection. Although availability is unaffected, the reputational damage and potential data leakage could have significant consequences, especially for enterprises handling sensitive personal data under GDPR. Organizations relying heavily on SAP Business Server Pages for critical business processes may face increased risk of targeted phishing campaigns exploiting this vulnerability. The lack of authentication requirement and ease of exploitation via crafted URLs increase the attack surface. However, the necessity of user interaction limits automated exploitation. Overall, the impact is medium but could escalate if combined with other attack vectors or social engineering tactics.

CWE-601URL Redirection to Untrusted Site ('Open Redirect') (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.5 (opens in a new tab)
Attack patterns
Cross-Site Flashing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Feb 2026, 09:47 UTC

WeaknessesCWE-601

Technical details

References

Community reviews

Related threats