CVE-2017-14077: Securimage HTML Injection

dapphp/securimage Updated 02 Oct 2025

Summary

13/05/2022
Yes i
Moderate
6.1

CVE-2017-14077: Securimage HTML Injection. Affects dapphp/securimage versions < 3.6.6. Fixed in 3.6.6. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Securimage is a package available on Packagist that provides CAPTCHA functionality for PHP applications. It is designed to prevent automated form submissions by generating and validating CAPTCHA images. However, prior to version 3.6.6, Securimage is vulnerable to HTML Injection attacks. This vulnerability allows remote attackers to inject arbitrary HTML into an email message body by manipulating the $_SERVER['HTTP_USER_AGENT'] parameter in the example_form.ajax.php or example_form.php files.

Vulnerability Detail

The HTML Injection vulnerability in Securimage can be exploited by an attacker to inject malicious HTML code into an email message body. This can lead to various consequences, such as phishing attacks, cross-site scripting (XSS), or the disclosure of sensitive information. The vulnerability originates from improper input sanitization and validation in the affected files. By manipulating the $_SERVER['HTTP_USER_AGENT'] parameter, an attacker can inject arbitrary HTML code into the email message body, potentially tricking users into performing unintended actions or disclosing sensitive information.

How To Fix

Minimum fixed version

3.6.6

This is the first release that contains the fix.

composer require dapphp/securimage:3.6.6

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If updating to the latest version is not immediately feasible, a temporary workaround can be implemented by manually sanitizing and validating the $_SERVER['HTTP_USER_AGENT'] parameter in the affected files. This can be done by using appropriate input sanitization functions or libraries, such as htmlspecialchars() or filter_var(), to ensure that any user-supplied input is properly encoded and does not contain malicious HTML code.

Conclusion

In conclusion, Securimage prior to version 3.6.6 is vulnerable to HTML Injection attacks. It is crucial to update the package to the latest version or apply appropriate input sanitization and validation to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for dapphp/securimage →

Share this vulnerability

FAQ

Securimage is a package available on Packagist that provides CAPTCHA functionality for PHP applications. It helps prevent automated form submissions by generating and validating CAPTCHA images.

HTML Injection is a type of vulnerability that allows an attacker to inject arbitrary HTML code into a web application. This can lead to various consequences, such as phishing attacks, cross-site scripting (XSS), or the disclosure of sensitive information.

This vulnerability can be exploited by manipulating the $_SERVER['HTTP_USER_AGENT'] parameter in the example_form.ajax.php or example_form.php files of Securimage. By injecting malicious HTML code into the email message body, an attacker can trick users into performing unintended actions or disclosing sensitive information.

The impact of this vulnerability can vary depending on the attacker's intentions. Possible consequences include phishing attacks, cross-site scripting (XSS), or the disclosure of sensitive information.

To fix this vulnerability, it is recommended to update Securimage to version 3.6.6 or later. This version includes the necessary fixes to properly sanitize and validate user input, preventing HTML Injection attacks.

How To Fix

Minimum fixed version

3.6.6

This is the first release that contains the fix.

composer require dapphp/securimage:3.6.6

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback