dbcve.org
PearwebApplication · Pear

CVE-2026-25241

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, an unauthenticated SQL injection in the /get/<package>/<version> endpoint allows remote attackers to execute arbitrary SQL via a crafted package version. 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

An unauthenticated SQL injection vulnerability exists in PEAR versions prior to 1.33.0. The /get/<package>/<version> endpoint fails to properly sanitize the version parameter before using it in SQL queries, allowing remote attackers to inject and execute arbitrary SQL commands. The vulnerability is exploitable without authentication and has a CVSS score of 9.8, indicating critical severity with potential for complete system compromise.

MitigationUpgrade PEAR to version 1.33.0 or later to apply the security patch. If immediate upgrade is not feasible, implement input validation on the version parameter and consider deploying a WAF with SQL injection detection rules as a temporary compensating control.

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 if Pear Pearweb is installed
    Check for the presence of Pear Pearweb installation by searching for pearweb files or the PEAR package manager. Common locations include /usr/share/pear, /var/www/pear, or the web server document root. Look for pearweb-specific directories or files.
    Affected if Pear Pearweb is found on the system and the version is below 1.33.0 or cannot be determined.
  2. Determine the installed Pear Pearweb version
    If Pear Pearweb is installed, locate its version information. This may be in a VERSION file, composer.json, or by running 'pear version' or 'pear info pear/pearweb' if the PEAR command-line tool is available. Check the package metadata or changelog for version details.
    Affected if The installed version is less than 1.33.0 or the version cannot be verified.
  3. Verify the vulnerable endpoint is exposed
    Check if the web server exposes the /get/<package>/<version> endpoint. This typically requires the PEAR web interface (pearweb) to be running as part of the PEAR installation. Inspect the web server configuration to determine if pearweb routes are accessible.
    Affected if The /get/ endpoint is accessible from the network and Pear Pearweb version is below 1.33.0.
  4. Inspect version parameter handling
    If code access is available, review the source code handling the /get/<package>/<version> route, specifically how the version parameter is processed before being used in database queries. Look for direct insertion of the version parameter into SQL statements without sanitization or parameterized queries.
    Affected if The version parameter is used directly in SQL queries without proper escaping, prepared statements, or input validation.

The environment is affected if Pear Pearweb is installed with a version below 1.33.0 and the /get/ endpoint is accessible, as the unauthenticated SQL injection can be exploited through the version parameter.

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 to apply the security patch. If immediate upgrade is not feasible, implement input validation on the version parameter and consider deploying a WAF with SQL injection detection rules as a temporary compensating control.

Recommended fix High confidence

1.33.0

  1. Backup your existing Pearweb installation and database before upgrading
  2. Download Pearweb version 1.33.0 from the official repository
  3. Replace the existing Pearweb files with the new version 1.33.0
  4. Verify that the /get/<package>/<version> endpoint no longer accepts malicious SQL payloads
  5. Test that normal package retrieval functionality continues to work correctly

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

Fix this in Pearweb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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