CVE-2017-14077 is a medium-severity (CVSS 6.1) Code Injection vulnerability in dapphp/securimage. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for dapphp/securimage — see the affected versions and patch details below.
Securimage HTML Injection
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
dapphp/securimageReal-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
HTML Injection in Securimage 3.6.4 and earlier allows remote attackers to inject arbitrary HTML into an e-mail message body via the $_SERVER['HTTP_USER_AGENT'] parameter to example_form.ajax.php or example_form.php.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | dapphp/securimage | all versions | 3.6.6composer require dapphp/securimage:^3.6.6 |
Affected Products
securimagephpcaptchaResearch 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 dapphp/securimage, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dapphp/securimage to 3.6.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-14077 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2017-14077 in your dependencies?
Find it across Packagist, including transitive dependencies.