CVE-2015-10029 is a critical-severity (CVSS 9.8) XML External Entity (XXE) vulnerability in kelvinmo/simplexrd. A fix is available for kelvinmo/simplexrd — see the affected versions and patch details below.
kelvinmo simplexrd vulnerable to Improper Restriction of XML External Entity Reference
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
kelvinmo/simplexrdReal-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 classified as problematic was found in kelvinmo simplexrd up to 3.1.0. This vulnerability affects unknown code of the file simplexrd/simplexrd.class.php. The manipulation leads to xml external entity reference. Upgrading to version 3.1.1 is able to address this issue. The name of the patch is 4c9f2e028523ed705b555eca2c18c64e71f1a35d. It is recommended to upgrade the affected component. VDB-217630 is the identifier assigned to this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | kelvinmo/simplexrd | all versions | 3.1.1composer require kelvinmo/simplexrd:^3.1.1 |
Affected Products
simplexrdsimplexrd_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kelvinmo/simplexrd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update kelvinmo/simplexrd to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-10029 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2015-10029 in your dependencies?
Find it across Packagist, including transitive dependencies.