CVE-2025-43916
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:NSummary
CVE-2025-43916 is a low-severity Use of Non-Canonical URL Paths for Authorization Decisions (CWE-647) vulnerability. Its CVSS base score is 3.4 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-12378
Vulnerability Data
Sonos api.sonos.com through 2025-04-21, when the /login/v3/oauth endpoint is used, accepts a redirect_uri containing userinfo in the authority component, which is not consistent with RFC 6819 section 5.2.3.5. An authorization code may be sent to an attacker-controlled destination. This might…
more
have further implications in conjunction with "Decompiling the app revealed a hardcoded secret."
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V2.2.1V10.4.1
Mitigating Controls (NIST 800-53 r5) AI
Proper enforcement of authorization decisions requires canonical URL normalization before policy evaluation, directly stopping non-canonical bypasses.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing well-defined authorization policies prevents URL canonicalization bypasses when path handling is included in the implementation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can discover non-canonical URL bypasses but does not itself implement the preventive control.
Defining application security requirements that mandate canonical URL handling and authorization checks mitigates the weakness at design time.
Secure-coding standards that require URL canonicalization and safe path handling eliminate the root cause of the weakness.
Enforcing strict access-control rules on canonical resource identifiers directly prevents authorization bypass via non-canonical URLs.