CVE-2022-24982
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 allows a remote authenticated attacker to access the cleartext credentials of all other form users. admin.php contains a hidden base64-encoded string with these credentials.
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 prior to February 2022 contain an information disclosure vulnerability in admin.php where user credentials are stored as a hidden base64-encoded (not encrypted) string. An authenticated remote attacker can access this endpoint to view cleartext credentials of all other form users.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify JQueryForm installationLocate jqueryform files or the jqueryform Jqueryform product in your environment. Look for the admin.php file mentioned in the CVE.Affected if JQueryForm is present and admin.php file exists in the environment
-
Determine installed versionCheck the version number of the Jqueryform Jqueryform installation. Compare it against the affected range of versions prior to 2022-02-05.Affected if The installed version is any version released before February 5, 2022 (versions earlier than the 2022-02-05 release)
-
Verify admin.php accessibilityAttempt to access the admin.php endpoint. The CVE indicates this endpoint is accessible to authenticated users and stores user credentials.Affected if The admin.php endpoint responds and is accessible to authenticated users in your environment
-
Inspect credential storage formatIf you have access to admin.php or the underlying data storage, examine how user credentials are stored. The CVE specifies credentials are stored as hidden base64-encoded strings rather than being encrypted.Affected if Credentials are stored in base64-encoded (not encrypted) format, which would be visible in cleartext after decoding
A user is affected if they have Jqueryform Jqueryform installed with a version released before 2022-02-05 and the admin.php endpoint is accessible to authenticated users, with credentials stored in base64-encoded format.
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
Organizations using JQueryForm.com forms should upgrade to versions released after 2022-02-05, force password resets for all affected user accounts, and audit logs for unauthorized credential access.
Regenerate forms using JQueryForm.com service dated 2022-02-05 or later
- Identify all forms generated by JQueryForm.com prior to 2022-02-05 in your environment
- Regenerate all affected forms using the JQueryForm.com service on or after 2022-02-05
- Replace all old vulnerable form instances with the newly generated secure forms
- Verify that the new admin.php files no longer contain hidden base64-encoded credential strings
- If credentials may have been compromised, rotate all exposed credentials immediately
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24982 — 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-24982 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