PHPApplication
CVE-2022-31631
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 · uneditedIn PHP versions 8.0.* before 8.0.27, 8.1.* before 8.1.15, 8.2.* before 8.2.2 when using PDO::quote() function to quote user-supplied data for SQLite, supplying an overly long string may cause the driver to incorrectly quote the data, which may further lead to SQL injection vulnerabilities.
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 confidenceIn PHP versions 8.0.x before 8.0.27, 8.1.x before 8.1.15, and 8.2.x before 8.2.2, the PDO::quote() function incorrectly handles overly long strings when quoting user-supplied data for SQLite databases, potentially leading to SQL injection vulnerabilities.
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
PHPApplication
>= 8.0.0, < 8.0.27>= 8.1.0, < 8.1.15>= 8.2.0, < 8.2.2CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Check installed PHP versionRun `php -v` on the command line or view phpinfo() output to determine the exact PHP versionAffected if Version is 8.0.x before 8.0.27, 8.1.x before 8.1.15, or 8.2.x before 8.2.2
-
Verify PDO SQLite extension is loadedRun `php -m` and look for PDO and pdo_sqlite modules, or check phpinfo() for PDO drivers sectionAffected if PDO driver for SQLite is present and loaded
-
Identify SQLite database connectionsSearch configuration files and application code for SQLite DSN strings containing 'sqlite:' or file paths to .db/.sqlite files used with PDOAffected if Application uses PDO to connect to SQLite databases
-
Check for PDO::quote() usage with SQLiteSearch application source code for calls to PDO::quote() method, particularly in files that handle SQLite database operationsAffected if Code calls PDO::quote() to escape user input when interacting with SQLite databases
You are affected if your PHP version is in the vulnerable range (8.0.x < 8.0.27, 8.1.x < 8.1.15, or 8.2.x < 8.2.2) AND your application uses PDO::quote() to escape user input for SQLite databases.
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 · scoped8.0.278.1.158.2.2
Upgrade PHP to version 8.0.27, 8.1.15, or 8.2.2 or later. As a temporary mitigation, replace PDO::quote() calls with parameterized queries/prepared statements.
PHP 8.0.27 (or latest 8.0.x), 8.1.15 (or latest 8.1.x), or 8.2.2 (or latest 8.2.x) depending on your current branch
- Check current PHP version by running 'php -v' on the server
- Identify which PHP 8.x branch is currently in use (8.0.x, 8.1.x, or 8.2.x)
- Update PHP to the minimum fixed version for your branch: 8.0.27, 8.1.15, or 8.2.2 respectively (or latest stable in the branch)
- For Ubuntu/Debian: run 'sudo apt update && sudo apt install php*' or specific version with 'sudo apt install php8.x'
- For RHEL/CentOS: run 'sudo yum update php' or 'sudo dnf update php'
- For Docker: update the PHP base image tag in your Dockerfile (e.g., change 'php:8.1' to 'php:8.1.15' or 'php:8.1.20')
- Verify the upgrade was successful by running 'php -v'
- Test application functionality, specifically any code using PDO::quote() with SQLite databases
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in PHP
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31631 — 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-31631 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