Quick answers
- Is CVE-2025-24876 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-24876 being exploited in the wild.
- How severe is CVE-2025-24876?
- Low severity, with a CVSS score of 3.1, published 11 February 2025.
- Which products and versions are affected?
- @sap/approuter (npm) SEMVER:introduced=2.6.1,fixed=16.7.2.
- Is there a fix for CVE-2025-24876?
- Yes. @sap/approuter (npm): upgrade to 16.7.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-24876 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-24876?
- Check whether you run @sap/approuter (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @sap/approuter (npm): upgrade to 16.7.2 or later
npm install @sap/approuter@16.7.2
Technical details
The vulnerability is a CWE-601 (Open Redirect/URL Redirection to Untrusted Site) authentication bypass affecting @sap/approuter versions 2.6.1 through 16.7.1. During the OAuth authorization code exchange, an attacker can inject malicious payloads to steal victim session tokens and bypass authentication controls. The attack requires user interaction (victim must complete the OAuth flow), but no authentication is required on the attacker's part. The vulnerability allows high-impact compromise of confidentiality and integrity. A patch is available in version 16.7.2 and later.
Affected products
- SAP Approuter 2.6.1 through 16.7.1
Identifiers
- CVE-2025-24876
- GHSA-cpfx-964w-4jvp
Timeline
- 2025-02-11: disclosed
- 2025-02-11: patched: Fixed in version 16.7.2