dbcve.org
PearwebApplication · Pear

CVE-2026-25237

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, use of preg_replace() with the /e modifier in bug update email handling can enable PHP code execution if attacker-controlled content reaches the evaluated replacement. 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

PEAR versions prior to 1.33.0 contain a code execution vulnerability in the bug update email handling functionality. The preg_replace() function is used with the /e modifier, which evaluates the replacement string as PHP code. When attacker-controlled input reaches this evaluated replacement, arbitrary PHP code can be executed on the server.

MitigationUpgrade PEAR to version 1.33.0 or later, which replaces the vulnerable preg_replace() /e usage with a secure alternative. Audit all code paths where user input could reach email processing logic.

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 installed Pearweb version
    Locate the Pearweb version file or header (typically found in the main PEAR index file, release notes, or version definition file). Common locations include a VERSION file, a version.php constant, or the PEAR info page accessible via the web interface.
    Affected if The installed version is any version prior to 1.33.0 (e.g., 1.32.x, 1.31.x, etc.)
  2. Locate the bug update email handling code
    Search the Pearweb source code for the preg_replace function call that processes email content related to bug updates. Look in email-related modules, handlers, or controllers that process incoming bug report notifications.
    Affected if A preg_replace() call using the /e modifier exists in files that handle bug update email processing
  3. Verify user input can reach the vulnerable preg_replace
    Examine the code path from email input (typically from $_POST, $_GET, or email parsing functions) to the identified preg_replace /e call. Check if the bug email handler accepts external input without sanitization before passing it to the replacement string.
    Affected if Unfiltered user-controlled data from bug update emails can flow into the evaluated replacement string in preg_replace /e

A user is affected if their Pearweb installation is version 1.33.0 or lower AND the bug update email handling code contains the vulnerable preg_replace /e pattern that processes attacker-supplied input.

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 PEAR to version 1.33.0 or later, which replaces the vulnerable preg_replace() /e usage with a secure alternative. Audit all code paths where user input could reach email processing logic.

Recommended fix High confidence

1.33.0

  1. 1. Back up the current Pearweb installation before making any changes
  2. 2. Download Pearweb version 1.33.0 from the official repository or source
  3. 3. Replace the existing Pearweb files with the new version 1.33.0
  4. 4. Verify the preg_replace() calls in bug update email handling no longer use the /e modifier
  5. 5. Test that the bug update email functionality works correctly after the upgrade
  6. 6. Monitor the application for any errors or unexpected behavior

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

Fix this in Pearweb Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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