CVE-2022-0813
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 · uneditedPhpMyAdmin 5.1.1 and before allows an attacker to retrieve potentially sensitive information by creating invalid requests. This affects the lang parameter, the pma_parameter, and the cookie section.
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 confidenceThis is an information disclosure vulnerability in PhpMyAdmin where invalid requests to the lang parameter, pma_parameter, and cookie sections allow unauthenticated attackers to retrieve potentially sensitive information. The vulnerability stems from improper error handling or input validation that leaks details in error responses.
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<= 5.1.1CVSS 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 the installed phpMyAdmin versionCheck the phpMyAdmin login page footer or check the version file (typically located at /libraries/Config.php or similar version-defining file in the phpMyAdmin directory)Affected if The installed version is 5.1.1 or any version <= 5.1.1
-
Test the lang parameter for information leakageSend an HTTP request to the phpMyAdmin index page with an invalid or malformed lang parameter value (e.g., ?lang=../../../../etc/passwd or ?lang=invalid<>) and observe the responseAffected if The server response contains sensitive information such as file paths, system configuration details, or stack traces that should not be exposed
-
Test the pma_parameter for information leakageSend an HTTP request with an invalid pma_parameter value (e.g., ?pma_parameter=<script> or ?pma_parameter=../../config) and examine any error messages returnedAffected if Error responses reveal internal paths, database configuration details, or other sensitive system information
-
Test cookie-based information disclosureModify phpMyAdmin cookies with invalid or malformed values and observe the response for leaked information in error messages or debug outputAffected if Invalid cookie values trigger error responses that expose sensitive configuration data, file paths, or session information
A system is affected if it runs phpMyAdmin version 5.1.1 or lower AND responds to invalid input in the lang, pma_parameter, or cookie parameters with sensitive information in error messages.
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 PhpMyAdmin to a version newer than 5.1.1 to receive the security patch, or implement input validation and proper error handling around the affected parameters to prevent information leakage.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0813 — 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-0813 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