CVE-2026-25235
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 · uneditedPEAR 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.
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 · moderate confidencePEAR versions prior to 1.33.0 contain predictable verification hashes in their election account request system. Attackers can exploit the weak random number generation to guess verification tokens and bypass authorization controls, potentially allowing unauthorized account verification.
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< 1.33.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Pearweb installation and versionLocate the Pearweb installation directory and check the version file or package metadata. Common locations include the web root or PEAR installation path. Look for a version identifier in the main Pearweb script or a VERSION file.Affected if The installed Pearweb version is below 1.33.0
-
Compare installed version to affected rangeReview the identified version number against the affected range. Versions prior to 1.33.0 contain the vulnerability.Affected if Running any version less than 1.33.0
-
Verify election account request system is accessibleCheck if the election account request feature is enabled and accessible in the Pearweb installation. This is typically found in the web-facing portion of the application.Affected if The election account request system is active and reachable via the web interface
-
Inspect random number generation in verification codeExamine the source code responsible for generating verification tokens in the account request system. Look for use of weak or predictable random number generation functions.Affected if The code uses predictable random number generation for verification token creation
User is affected if running Pearweb version below 1.33.0 and the election account request system is accessible, as the predictable hash vulnerability allows token guessing for authorization bypass.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.33.0
Upgrade PEAR to version 1.33.0 or later to apply the patch that fixes the predictable hash vulnerability.
1.33.0
- 1. Back up your current Pearweb installation and database before upgrading.
- 2. Download Pearweb version 1.33.0 from the official PEAR repository or GitHub releases.
- 3. Replace the existing Pearweb files with the new version 1.33.0 files.
- 4. Verify file permissions are correctly set after the upgrade.
- 5. Test that the application functions normally after the upgrade.
- 6. Verify that the predictably-generated verification hashes have been replaced with secure random tokens in the new version.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-25235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25235 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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