CVE-2010-10004 — simplesamlphp-module-info…
MEDIUMFix: simplesamlphp/simplesamlphp-module-infocard@f6bfea4CVE-2010-10004 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in simplesamlphp/simplesamlphp-module-infocard. A fix is available for simplesamlphp/simplesamlphp-module-infocard — see the affected versions and patch details below.
Information Cards Module vulnerable to Cross-site Scripting
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
simplesamlphp/simplesamlphp-module-infocardReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
A vulnerability was found in Information Cards Module on simpleSAMLphp and classified as problematic. This issue affects some unknown processing. The manipulation leads to cross site scripting. The attack may be initiated remotely. Upgrading to version 1.0 is able to address this issue. The identifier of the patch is f6bfea49ae16dc6e179df8306d39c3694f1ef186. It is recommended to upgrade the affected component. The identifier VDB-217661 was assigned to this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | simplesamlphp/simplesamlphp-module-infocard | all versions | 1.0composer require simplesamlphp/simplesamlphp-module-infocard:^1.0 |
Affected Products
information cards modulesimplesamlphpDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for simplesamlphp/simplesamlphp-module-infocard, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update simplesamlphp/simplesamlphp-module-infocard to 1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-10004 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2010-10004 in your dependencies?
Find it across Packagist, including transitive dependencies.