CVE-2018-1999022
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 · uneditedPEAR HTML_QuickForm version 3.2.14 contains an eval injection (CWE-95) vulnerability in HTML_QuickForm's getSubmitValue method, HTML_QuickForm's validate method, HTML_QuickForm_hierselect's _setOptions method, HTML_QuickForm_element's _findValue method, HTML_QuickForm_element's _prepareValue method. that can result in Possible information disclosure, possible impact on data integrity and execution of arbitrary code. This attack appear to be exploitable via A specially crafted query string could be utilised, e.g. http://www.example.com/admin/add_practice_type_id[1]=fubar%27])%20OR%20die(%27OOK!%27);%20//&mode=live. This vulnerability appears to have been fixed in 3.2.15.
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 · high confidencePEAR HTML_QuickForm version 3.2.14 contains an eval injection (CWE-95) vulnerability affecting multiple methods (getSubmitValue, validate, _setOptions, _findValue, _prepareValue). Attackers can execute arbitrary PHP code via specially crafted query string parameters, potentially leading to information disclosure, data integrity compromise, and remote code execution.
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= 3.2.14<= 4.6.37= 5.3.0CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify HTML_QuickForm versionLocate the HTML/QuickForm.php file and check the version defined in the file header or package.xml. Common paths include vendor/html_quickform/ or include paths. Run: grep -r 'version' QuickForm.php | head -5Affected if version equals 3.2.14 exactly (only this specific version is vulnerable)
-
Identify Civicrm version if installedCheck Civicrm version by looking at civicrm-version.php in the civicrm root directory, or run: grep CRM_VERSION civicrm-version.php or check database civicrm_domain table. Also check composer.json or package.json for civicrm version entry.Affected if civicrm version is <= 4.6.37 or exactly 5.3.0
-
Confirm PHP code uses QuickForm methodsSearch codebase for usage of the vulnerable methods: getSubmitValue, validate, _setOptions, _findValue, _prepareValue. Run: grep -rn 'getSubmitValue\|validate\|_setOptions\|_findValue\|_prepareValue' --include='*.php'Affected if any of these methods are called in your PHP application code
-
Check if query parameters reach QuickForm processingTrace how $_GET, $_POST, or $_REQUEST superglobals flow into QuickForm method calls. Look for direct assignment of request parameters to QuickForm elements without sanitization. Review form handling code that processes user input.Affected if query string parameters are passed directly to QuickForm processing without input validation
You are affected if you have HTML_QuickForm 3.2.14 OR Civicrm <= 4.6.37/5.3.0 AND user-supplied query parameters reach the vulnerable methods.
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.
dbcve · scopedUpgrade to HTML_QuickForm version 3.2.15 or later. If immediate upgrade is not feasible, implement rigorous input validation and sanitization on all query string parameters before they reach any QuickForm processing logic.
HTML_QuickForm 3.2.15 or Civicrm 4.6.38+/5.4.0+
- Identify all locations where PEAR HTML_QuickForm version 3.2.14 is used in your project dependencies
- Upgrade PEAR HTML_QuickForm to version 3.2.15 using your package manager (e.g., pear upgrade HTML_QuickForm-3.2.15 or via composer if available)
- If using Composer, run 'composer update pear/html_quickform' to get the fixed version
- Verify the upgrade was successful by checking the installed version
- Test your application's forms and validation functionality to ensure the upgrade does not break existing features
- For Civicrm users: Ensure Civicrm is updated to a version that includes the fixed HTML_QuickForm dependency (version 4.6.38 or later, or 5.4.0 or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing8.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1999022 — 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-2018-1999022 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