dbcve.org
PearwebApplication · Pear

CVE-2026-25238

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 vulnerability in bug subscription deletion may allow attackers to inject SQL via a crafted email 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 confidence

A SQL injection vulnerability exists in the bug subscription deletion feature of PEAR (PHP Extension and Application Repository) versions prior to 1.33.0. Attackers can inject malicious SQL commands through a crafted email value in the subscription deletion functionality. This critical vulnerability (CVSS 9.8) allows unauthenticated attackers to potentially access, modify, or delete database content.

MitigationUpgrade to PEAR version 1.33.0 or later, which contains the patch for this SQL injection vulnerability. Until the upgrade is completed, implement input validation and parameterized queries for all email-related database operations.

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. Identify Pear Pearweb installation and version
    Locate the pearweb installation directory and check the version file or package.xml for the installed version. Common locations include /usr/share/pear or via 'pear info' command if pearweb is installed as a PEAR package.
    Affected if The installed version is less than 1.33.0
  2. Verify bug subscription deletion feature is accessible
    Check if the bug subscription deletion functionality is enabled in the PEAR bug tracker web interface. This typically involves checking the web application's routing or module configuration for the subscription handling code.
    Affected if The bug subscription deletion feature is accessible and operational in the application
  3. Inspect subscription deletion code for parameter handling
    Locate the script or file handling the bug subscription deletion request (typically a PHP file processing the email parameter). Examine how the email value from the request is incorporated into SQL queries.
    Affected if The email parameter is used directly in SQL queries without proper sanitization or parameterized queries
  4. Confirm database interaction exists
    Verify that the subscription deletion functionality interacts with a database and that the application's database configuration is present and active.
    Affected if The application uses a database backend for bug tracking and the subscription feature queries that database using user-supplied input

A user is affected if they are running Pear Pearweb version below 1.33.0 and the bug subscription deletion feature is accessible, with the email parameter being directly interpolated into SQL queries without prepared statements or input sanitization.

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, which contains the patch for this SQL injection vulnerability. Until the upgrade is completed, implement input validation and parameterized queries for all email-related database operations.

Recommended fix Moderate confidence

1.33.0

  1. Download Pearweb version 1.33.0 from the official PEAR repository or GitHub releases
  2. Replace existing Pearweb installation files with the updated 1.33.0 version
  3. Verify the upgrade was successful by checking the version number in the installation
  4. Confirm the SQL injection vulnerability in bug subscription deletion is resolved by testing email handling in the bug subscription feature

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

Fix this in Pearweb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25238 — 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-25238 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