CVE-2022-46484
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 · uneditedInformation disclosure in password protected surveys in Data Illusion Survey Software Solutions NGSurvey v2.4.28 and below allows attackers to view the password to access and arbitrarily submit surveys.
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 confidenceThe vulnerability in NGSurvey v2.4.28 and below allows unauthenticated attackers to access the plaintext password protecting surveys through an information disclosure flaw. This enables unauthorized parties to view survey passwords and submit responses arbitrarily.
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<= 2.4.28CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 NGSurvey installation and versionLocate the NGSurvey installation directory and check the version file or application banner. Common locations include /opt/ngsurvey, /var/www/html/ngsurvey, or the application's about/version page.Affected if The installed version is 2.4.28 or lower.
-
Confirm password-protected surveys are in useAccess the NGSurvey admin panel or examine the survey configuration database/flat files to identify surveys that have password protection enabled.Affected if Any survey is configured with a password protection setting.
-
Check for unauthenticated password disclosureAttempt to access the survey password endpoint without authentication. The vulnerability allows retrieval of plaintext survey passwords via an unauthenticated request to the survey password endpoint or related API.Affected if Plaintext passwords for protected surveys can be retrieved without authentication.
-
Review access logs for password endpoint probingExamine web server access logs for unusual requests to survey password-related endpoints, particularly from unauthenticated sources or unusual IP addresses.Affected if Unauthenticated requests to password endpoints are present in logs.
You are affected if NGSurvey version 2.4.28 or lower is installed and password-protected surveys are configured, as the vulnerability allows unauthenticated attackers to retrieve plaintext survey passwords.
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 dataUpgrade to NGSurvey v2.4.28+ if available, otherwise disable password-protected surveys until a patch is released and implement monitoring for unauthorized survey submissions.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46484 — 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-46484 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