dbcve.org
PearwebApplication · Pear

CVE-2026-25233

CRITICAL · 9.1 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, logic bug in the roadmap role check allows non-lead maintainers to create, update, or delete roadmaps. 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 logic flaw in the role verification mechanism for roadmap management. The vulnerability permits non-lead maintainers to bypass authorization checks and perform create, update, or delete operations on roadmaps, representing a privilege escalation issue.

MitigationUpgrade PEAR to version 1.33.0 or later to obtain the patched role validation logic. Before deploying in production, verify that the upgrade does not break existing functionality.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 installation and check its version number, typically found in a version file, changelog, or package definition. Common locations include a VERSION file, composer.json, or the main Pearweb index/header file.
    Affected if The installed version is any version prior to 1.33.0 (e.g., 1.32.x, 1.31.x, etc.)
  2. Verify roadmap management feature is enabled
    Check the Pearweb configuration or module settings to determine if the roadmap management functionality is actively enabled on the installation. Look for roadmap-related configuration flags, modules, or plugins in the system.
    Affected if The roadmap management feature is enabled and accessible to users
  3. Confirm user role assignment mechanism exists
    Examine the user management system to identify how roles are assigned, particularly the distinction between lead maintainers and non-lead maintainers. Check role definition files or database records that define user permissions.
    Affected if The system has a role-based access control (RBAC) mechanism where users can be assigned different permission levels for roadmap operations
  4. Identify non-lead maintainer accounts
    Review user accounts in the system to determine if there are any users assigned roles other than lead maintainer who have access to the roadmap functionality. Check user role mappings or permission tables.
    Affected if Non-lead maintainer accounts exist with access to the roadmap feature, enabling potential exploitation of the authorization bypass

A user is affected if running Pearweb version prior to 1.33.0 with the roadmap management feature enabled and non-lead maintainer accounts present in the system.

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 obtain the patched role validation logic. Before deploying in production, verify that the upgrade does not break existing functionality.

Recommended fix High confidence

1.33.0

  1. Backup the existing Pearweb installation and database before proceeding
  2. Download Pearweb version 1.33.0 from the official source (pear.php.net or the PEAR GitHub repository)
  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 roadmap role check now properly restricts non-lead maintainers from creating, updating, or deleting roadmaps

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

Fix this in Pearweb Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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