CVE-2022-24981
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 · uneditedA reflected cross-site scripting (XSS) vulnerability in forms generated by JQueryForm.com before 2022-02-05 allows remote attackers to inject arbitrary web script or HTML via the redirect parameter to admin.php.
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 confidenceA reflected cross-site scripting (XSS) vulnerability in JQueryForm.com allows remote attackers to inject arbitrary web script or HTML via the redirect parameter to admin.php. The vulnerability exists because user-supplied input in the redirect parameter is not properly sanitized or encoded before being reflected in the application's response.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 the admin.php scriptSearch for admin.php in your web root directories or application deployment paths. This is the file that handles the vulnerable redirect parameter.Affected if admin.php exists and is accessible via the web server
-
Identify the Jqueryform versionCheck the version file, changelog, or composer.json/package.json in your deployment for the installed Jqueryform version and compare it to the fix date 2022-02-05. Earlier versions are affected.Affected if The installed version predates February 5, 2022 or the version number is below the patched release
-
Verify admin.php accepts redirect parameterSend a test request to admin.php with a benign redirect parameter such as ?redirect=test to see if it reflects the value in the response without encoding.Affected if The redirect parameter value appears unescaped in the HTML response (e.g., <a href="test"> or the raw value visible in the page source)
-
Check if admin.php is publicly accessibleReview your web server configuration or access logs to confirm whether admin.php is reachable from untrusted networks or if it is restricted to authenticated/local users only.Affected if admin.php is exposed to unauthenticated or untrusted users
You are affected if Jqueryform version is before 2022-02-05, admin.php is accessible, and the redirect parameter reflects input without HTML encoding.
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 proper input validation and output encoding on the redirect parameter in admin.php to ensure user-supplied data is safely rendered. Consider using a whitelist approach for allowed redirect URLs or applying context-appropriate encoding before reflecting any user input.
Use JQueryForm.com service to generate forms dated 2022-02-05 or later (any form generated on or after this date includes the XSS fix)
- Identify all forms generated by JQueryForm.com that were created before 2022-02-05
- Regenerate these forms using the current JQueryForm.com service (which now has the fix dated 2022-02-05 or later)
- Replace the old vulnerable form code with the newly generated fixed versions on your website
- Verify that the redirect parameter in admin.php properly sanitizes user input and does not allow XSS payloads
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24981 — 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-24981 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