CVE-2026-25240
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 · uneditedPEAR is a framework and distribution system for reusable PHP components. Prior to version 1.33.0, a SQL injection vulnerability can occur in user::maintains() when role filters are provided as an array and interpolated into an IN (...) clause. This issue has been patched in version 1.33.0.
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 confidenceSQL injection vulnerability in PEAR's user::maintains() function where role filter arrays are directly interpolated into an IN (...) clause without proper parameterization, allowing attacker-controlled input to manipulate SQL queries.
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< 1.33.0CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Pear Pearweb versionLocate the Pear Pearweb installation and determine its version number, typically found in version files, composer.json, or release documentationAffected if The installed version is below 1.33.0
-
Locate user::maintains() functionSearch the codebase for the maintains() function within user-related class filesAffected if The function exists in the codebase and processes role filter arrays
-
Inspect role filter array handlingExamine the maintains() function code to see if role filter arrays are interpolated directly into SQL IN (...) clauses without parameterizationAffected if Role filter arrays are concatenated directly into SQL queries without proper escaping or parameterized queries
-
Verify input to maintains()Trace how data reaches the maintains() function, particularly the role filter parameter, to confirm user-controlled input can reach the vulnerable code pathAffected if The role filter parameter accepts user-supplied values that flow into the unsanitized SQL construction
You are affected if Pear Pearweb version is below 1.33.0 and the user::maintains() function directly interpolates role filter arrays into SQL IN clauses without parameterization.
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 · scoped1.33.0
Upgrade PEAR to version 1.33.0 or later which contains the patched code. If immediate upgrade is not possible, sanitize and validate role filter arrays before passing to maintains().
1.33.0
- 1. Identify the Pearweb installation directory in your environment
- 2. Check the current installed version of Pearweb (likely in a VERSION file or package.xml)
- 3. Confirm the current version is below 1.33.0
- 4. Back up the current Pearweb installation and database
- 5. Upgrade to version 1.33.0 or later using your package manager (pear upgrade) or by downloading from the official PEAR repository
- 6. Verify the upgrade was successful by checking the new version
- 7. Test the user::maintains() function to ensure normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25240 — 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-2026-25240 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