Skip to main content

Pear CVE-2026-25235

HIGH
Predictable Seed in Pseudo-Random Number Generator (PRNG) (CWE-337)
2026-02-03 security-advisories@github.com
7.5
CVSS 3.1 · GitHub Advisory
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify predictable verification hash algorithm
  2. Exploit
    Enumerate weak token space
  3. Execution
    Guess valid verification tokens
  4. Impact
    Bypass election account authorization checks

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Unpredictable PRNG seeds
Exploitation Conditions

PEAR versions prior to 1.33.0 with election account verification feature enabled. Attacker must have network access to the PEAR installation endpoint accepting verification token submissions. No authentication required.

Impact

CVSS 7.5 (HIGH). Attack vector: Network. Complexity: Low. Privileges required: None. User interaction: None. Exploitation no authentication required.

Exploit ScenarioDerived

An attacker without authentication could exploit this vulnerability to guess verification tokens and potentially verify election account requests witho.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Pearweb versions up to 1.33.0 contains a vulnerability that allows attackers to guess verification tokens and potentially verify election account requests witho (CVSS 7.5).

RemediationAI

Fixed in version 1.33.0.. Restrict network access to the affected service where possible.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

affects Pearweb. PEAR is a framework and distribution system for reusable PHP components. Prior to version 1.33.0, predictable verification hashes may allow attackers to guess verification tokens and potentially verify election account requests without authorization. This issue has been patched in version 1.33.0.

Know when Pear gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionGitHub Advisory

PEAR is a framework and distribution system for reusable PHP components. Prior to version 1.33.0, predictable verification hashes may allow attackers to guess verification tokens and potentially verify election account requests without authorization. This issue has been patched in version 1.33.0.

Executive ViewAI

Why It Matters

Pearweb versions up to 1.33.0 contain a vulnerability allowing attackers to bypass election account verification controls by guessing security tokens. This directly threatens the integrity of election-related processes and could enable unauthorized account access, potentially compromising electoral data and system credibility.

Business Impact: High
Compensating Controls

Implement Web Application Firewall (WAF) rules to detect and block brute-force attempts against verification endpoints; enforce strict rate limiting on token submission (max 3 attempts per 15 minutes); add CAPTCHA challenges to verification forms; disable Pearweb's public-facing verification features if not operationally critical; restrict network access to Pearweb to trusted IP ranges only; implement token expiration windows shorter than current default; increase monitoring and alerting on account verification failures.

Threat Intelligence Overview

EPSS Score
0.0%
Top 86% exploitable
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Affected Products (CPE)GitHub Advisory

cpe:2.3:a:pear:pearweb:*:*:*:*:*:*:*:*

More in Pear

View all
CVE-2017-5630 HIGH POC
7.5 Feb 01

PECL in the download utility class in the Installer in PEAR Base System v1.10.1 does not validate file types and filenam

CVE-2017-5677 CRITICAL
9.8 Feb 06

PEAR HTML_AJAX 0.3.0 through 0.5.7 has a PHP Object Injection Vulnerability in the PHP Serializer. Rated critical severi

CVE-2026-25237 CRITICAL
9.8 Feb 03

PEAR PHP framework has a code execution vulnerability through unsafe use of preg_replace() that allows attackers to exec

CVE-2026-25241 CRITICAL
9.8 Feb 03

PEAR PHP framework has a seventh SQL injection with higher EPSS (0.12%), indicating more active scanning for this partic

CVE-2026-25240 CRITICAL
9.8 Feb 03

PEAR PHP framework has another SQL injection vulnerability prior to version 1.33.0, the sixth in a series of critical se

CVE-2026-25238 CRITICAL
9.8 Feb 03

PEAR PHP framework prior to 1.33.0 has a fifth SQL injection vulnerability, part of a comprehensive security audit that

CVE-2026-25236 CRITICAL
9.8 Feb 03

PEAR PHP framework has a second SQL injection vulnerability in a different code path, providing an alternate database co

CVE-2026-25234 CRITICAL
9.8 Feb 03

PEAR PHP framework prior to 1.33.0 has a SQL injection vulnerability allowing attackers to extract data from the compone

CVE-2026-25233 CRITICAL
9.1 Feb 03

PEAR PHP framework prior to 1.33.0 has a logic bug in the roadmap feature allowing unauthorized access through incorrect

CVE-2026-25239 HIGH
7.5 Feb 03

SQL injection in PEAR's apidoc queue insertion allows unauthenticated remote attackers to manipulate database queries by

CVE-2022-24953 MEDIUM
5.3 Feb 17

The Crypt_GPG extension before 1.6.7 for PHP does not prevent additional options in GPG calls, which presents a risk for

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy