CVE-2022-24984
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 · uneditedForms generated by JQueryForm.com before 2022-02-05 (if file-upload capability is enabled) allow remote unauthenticated attackers to upload executable files and achieve remote code execution. This occurs because file-extension checks occur on the client side, and because not all executable content (e.g., .phtml or .php.bak) is blocked.
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 confidenceForms generated by JQueryForm.com before February 2022 with file-upload enabled perform file-extension validation only on the client side, allowing attackers to bypass this check and upload executable files (.phtml, .php.bak, etc.) that achieve remote code execution when accessed.
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< 2022-02-05CVSS 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.1/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 JQueryForm usageSearch your codebase and web assets for references to jqueryform.com or the jqueryform library (jquery.form.js or similar). Check your form HTML for the jqueryform plugin initialization.Affected if JQueryForm from jqueryform.com is in use
-
Check form generation dateIf using jqueryform.com to generate forms, look at the form creation date or the timestamp in the form files. Forms generated before February 5, 2022 are potentially affected.Affected if Forms were generated before February 5, 2022
-
Verify file upload is enabledInspect your JQueryForm configuration and HTML forms to determine if the file upload feature is enabled (look for input type='file' elements within jqueryform-enabled forms).Affected if File upload functionality is enabled on any JQueryForm form
-
Inspect file validation implementationExamine the server-side code that handles uploaded files. Look for file extension validation happening on the server. Check if only client-side JavaScript validation exists (the vulnerable condition).Affected if Only client-side file extension validation is present and no server-side validation exists
-
Audit existing uploaded filesScan your upload directories for files with executable extensions such as .phtml, .php, .php.bak, .php3, .php5, .php7, .phar, or other script extensions that could lead to code execution.Affected if Any executable file types (.phtml, .php variants, etc.) are found in upload directories
You are affected if you use JQueryForm from jqueryform.com with forms generated before February 5, 2022 that have file upload enabled and lack server-side file validation.
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 · scoped2022-02-05
Implement server-side file validation to verify file types, block executable extensions, and consider migrating to a form solution that supports secure server-side file handling or disable file upload capability if not needed.
Version released on or after 2022-02-05
- 1. Identify all instances of JQueryForm in your application that have file-upload capability enabled
- 2. Check the JQueryForm library version or build date being used
- 3. If the version/build date is before 2022-02-05, upgrade to a version released on or after 2022-02-05
- 4. Verify that server-side file validation is implemented in addition to any client-side checks
- 5. Ensure that the server rejects executable file extensions (.php, .phtml, .php.bak, .exe, .asp, .jsp, etc.)
- 6. Test the file upload functionality to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24984 — 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-2022-24984 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