CVE-2012-0693
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedsubmitticket.php in WHMCompleteSolution (WHMCS) 5.03 allows remote attackers to inject arbitrary code into a subject field via crafted ticket data, a different vulnerability than CVE-2011-5061. NOTE: the vendor disputes this issue, noting that some of the details overlap CVE-2011-5061, but that it "says it affects V5.0.3, and the submitticket.php file, both of which are wrong.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceRemote code injection vulnerability in WHMCS submitticket.php allows attackers to inject arbitrary code into the ticket subject field. The application fails to properly sanitize user input in the subject parameter before processing or storing it, allowing PHP code execution. This is a classic input validation failure in a web forms.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.03CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate WHMCS installationSearch for the whmcs directory or configuration file (configuration.php) in the web root. Common paths include /var/www/html/whmcs/, /home/user/public_html/whmcs/, or C:\inetpub\wwwroot\whmcs\Affected if WHMCS software is present on the server and the installation directory is found
-
Identify installed WHMCS versionOpen the WHMCS configuration file (configuration.php) and look for the $version variable, or check the admin/login.php version indicator. The affected version is 5.03Affected if The installed version is exactly 5.03 (Whmcompletesolution)
-
Verify submitticket.php existsCheck for the presence of submitticket.php in the WHMCS web root, typically at /submitticket.php or /support/submitticket.phpAffected if The file submitticket.php exists and is accessible via web
-
Confirm ticket submission is enabledVerify that the support ticket system is active by checking the WHMCS admin configuration under Setup > Support > Ticket Departments or by confirming the /submitticket.php page loads without being disabledAffected if The ticket submission feature is enabled and the submitticket.php page is accessible to unauthenticated users
The environment is affected if WHMCS version 5.03 is installed and the ticket submission page (submitticket.php) is accessible with the subject input field available for user input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and output encoding for all ticket submission fields, particularly the subject field. Upgrade to a patched version of WHMCS and apply vendor-released security updates.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0693 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-0693 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data