CVE-2015-5243 is a critical-severity (CVSS 9.8) Code Injection vulnerability in jsmitty12/phpwhois. 1 public exploit reference exists, so weaponization risk is real. A fix is available for jsmitty12/phpwhois — see the affected versions and patch details below.
phpWhois arbitrary code execution via a crafted whois record
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2015-5243 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
jsmitty12/phpwhois🐘phpwhois/phpwhois🐘brightlocal/phpwhois🐘david-garcia/phpwhois🐘ivankristianto/phpwhois🐘kazist/phpwhois🐘serluck/phpwhois🐘simple-updates/phpwhois+1 moreReal-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
phpWhois allows remote attackers to execute arbitrary code via a crafted whois record.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | jsmitty12/phpwhois | all versions | 5.1.0composer require jsmitty12/phpwhois:^5.1.0 |
| 🐘Packagist | phpwhois/phpwhois | all versions | No fix |
| 🐘Packagist | brightlocal/phpwhois | all versions | No fix |
| 🐘Packagist | david-garcia/phpwhois | all versions | No fix |
| 🐘Packagist | ivankristianto/phpwhois | all versions | No fix |
| 🐘Packagist | kazist/phpwhois | all versions | No fix |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jsmitty12/phpwhois, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jsmitty12/phpwhois to 5.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-5243 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2015-5243 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2015-5243. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2015-5243 in your dependencies?
O3 Security finds CVE-2015-5243 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.