CVE-2026-25234
BaseFortify
Publication date: 2026-02-03
Last updated on: 2026-02-05
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| pear | pearweb | to 1.33.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-25234 is a SQL injection vulnerability in the PEAR framework, specifically in the category deletion functionality before version 1.33.0.
The vulnerability occurs because the category ID is directly included in the SQL query without proper sanitization or parameterization, allowing an attacker with access to the category manager workflow to inject malicious SQL code.
This flaw exists in the file `include/pear-database-category.php` and is triggered via a POST request handled by `public_html/admin/category-manager.php`.
The issue has been fixed in version 1.33.0 of PEAR.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute arbitrary SQL commands on the affected system.
As a result, unauthorized data access or modification may occur, potentially compromising the integrity and confidentiality of the database.
Since the attacker needs access to the category manager workflow, the impact depends on the level of access control in place.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by examining if your PEAR installation is running a version prior to 1.33.0 and if the category deletion functionality is accessible. Specifically, monitoring or testing the POST requests to the endpoint `public_html/admin/category-manager.php` that handle category or parent IDs can help identify attempts to exploit the SQL injection.'}, {'type': 'paragraph', 'content': 'To detect potential exploitation or test for the vulnerability, you can attempt to send crafted POST requests with SQL injection payloads in the category ID parameter to see if the system is vulnerable.'}, {'type': 'paragraph', 'content': 'Example command using curl to test for SQL injection in the category deletion parameter:'}, {'type': 'list_item', 'content': 'curl -X POST -d "category_id=1\' OR \'1\'=\'1" https://your-pear-instance/public_html/admin/category-manager.php'}, {'type': 'paragraph', 'content': 'Additionally, reviewing logs for unusual SQL errors or unexpected behavior during category deletion requests can help detect exploitation attempts.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate and recommended mitigation step is to upgrade the PEAR package to version 1.33.0 or later, where this SQL injection vulnerability has been patched.
If upgrading immediately is not possible, restrict access to the category manager workflow to trusted users only, as exploitation requires access to this functionality.
Additionally, monitor and audit POST requests to the category manager endpoint for suspicious input patterns and consider implementing web application firewall (WAF) rules to block SQL injection attempts targeting the category deletion parameters.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in PEAR prior to version 1.33.0 allows an attacker with access to the category manager workflow to execute arbitrary SQL commands, potentially leading to unauthorized data access or modification.
Such unauthorized access or modification of data could impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive data and prevention of unauthorized access.
However, the provided information does not explicitly discuss the direct effects on compliance with these standards.