dbcve.org
PearwebApplication · Pear

CVE-2026-25236

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 1.33.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
PEAR is a framework and distribution system for reusable PHP components. Prior to version 1.33.0, a SQL injection risk exists in karma queries due to unsafe literal substitution for an IN (...) list. 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 confidence

SQL injection vulnerability in PEAR's karma query system where unsafe literal substitution in IN (...) clauses allows attacker-controlled input to be directly inserted into SQL queries, enabling unauthorized database access.

MitigationUpgrade to PEAR version 1.33.0 or later to apply the patch; if immediate upgrade is not possible, identify and sanitize all karma-related query parameters that feed into IN clauses.

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
PearwebApplication
Affected:< 1.33.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm PEAR installation
    Run 'pear version' or check for PEAR installation directories (typically /usr/share/pear or C:\php\pear)
    Affected if PEAR/Pearweb is installed on the system
  2. Identify Pearweb version
    Check the Pearweb version file or run 'pear info pear/pearweb' if available, or inspect the version.php file in the Pearweb installation directory
    Affected if Installed version is below 1.33.0
  3. Verify karma module is active
    Inspect the Pearweb installation for karma-related files (typically in lib/ or includes/ directories, look for karma.php, karma.inc, or karma-related database tables)
    Affected if The karma module or system is present and enabled in the Pearweb installation
  4. Check for user-accessible karma query endpoints
    Review web server logs or application routing configuration for URLs or parameters that invoke karma query functionality (search for 'karma' in web access logs or application route files)
    Affected if Karma-related query parameters are accessible via HTTP requests to the application
  5. Inspect karma query code for IN clause usage
    If source code is accessible, search for SQL queries containing 'IN (' in karma-related PHP files, particularly looking for variables used within IN clauses without proper escaping or parameterization
    Affected if Code contains IN clause queries that use direct variable interpolation without prepared statements or escaping

A user is affected if Pearweb is installed with a version below 1.33.0 and the karma query system is active and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.33.0 or later
Fixed in 1.33.0
Interim mitigation

Upgrade to PEAR version 1.33.0 or later to apply the patch; if immediate upgrade is not possible, identify and sanitize all karma-related query parameters that feed into IN clauses.

Recommended fix Moderate confidence

1.33.0

  1. Identify the current Pearweb version installed in your environment
  2. Backup your current Pearweb installation and database before upgrading
  3. Use PEAR channel to upgrade: `pear upgrade pear/Pearweb` or download version 1.33.0 from the official PEAR repository
  4. Verify the upgrade completed successfully by checking the installed version: `pear info pear/Pearweb`
  5. Test that the karma-related functionality works correctly after upgrade
  6. Monitor application logs for any SQL errors or anomalies

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pearweb Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25236 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25236 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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