CVE-2026-25239
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 in apidoc queue insertion can allow query manipulation if an attacker can influence the inserted filename value. 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 confidenceA SQL injection vulnerability exists in PEAR's apidoc component where user-controllable filename values are inserted into database queries without proper sanitization. An attacker who can influence the filename parameter during apidoc queue insertion can manipulate SQL queries. This issue affects all versions prior to 1.33.0.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Identify installed Pearweb versionRun 'pear version' or check Pearweb package version using 'pear list' or inspect installed package metadataAffected if Version is below 1.33.0
-
Confirm apidoc component is accessibleCheck if the apidoc generation functionality is installed and accessible on the systemAffected if apidoc component is present and enabled
-
Verify database is in useInspect Pearweb configuration for database connectivity settings using 'pear config-get' or check configuration filesAffected if Database is configured (required for SQL injection to be exploitable)
-
Assess exposure to filename parameterDetermine if the apidoc queue insertion functionality is accessible to users or external callers who can supply the filename parameterAffected if Users can influence the filename parameter during apidoc queue insertion
System is affected if running Pearweb version below 1.33.0 with the apidoc component accessible, a database configured, and user-influenced filename input possible during queue insertion
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 to PEAR version 1.33.0 or later to apply the patch. If immediate upgrading is not feasible, implement parameterized queries or robust input validation on the filename parameter in the apidoc queue insertion code.
1.33.0
- Check the current Pearweb installation version by examining the version file or using the PEAR version command
- Download Pearweb version 1.33.0 from the official PEAR repository or GitHub releases
- Backup the existing Pearweb installation and database
- Replace the existing Pearweb files with the new version 1.33.0 files
- Run any database migration scripts if provided with the update
- Verify the upgrade was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25239 — 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-25239 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