dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-59133

HIGH · 7.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Custom role Insecure Direct Object References (IDOR) in Projectopia <= 5.1.25.2 versions.

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 confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in Projectopia's custom role functionality. The flaw allows authenticated users to potentially access or modify objects (resources, data, or functionality) they should not have authorization to access by manipulating object references, likely due to insufficient authorization validation on role-based operations.

MitigationUpgrade to a patched version of Projectopia beyond 5.1.25.2; if no patch is available, implement proper object-level authorization checks on all custom role operations and validate that the requesting user has explicit permission to access the referenced object.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Projectopia installation version
    Locate the Projectopia installation and check the version number, typically found in the application admin panel, a version file, or the codebase (often in a version.php, about page, or composer.json)
    Affected if The installed version is 5.1.25.2 or earlier (any version up to and including 5.1.25.2 is affected)
  2. Verify custom role functionality is in use
    Check if custom roles have been created or configured in the Projectopia system. Look for custom role definitions in the database (tables related to roles or permissions) or through the admin interface under role management
    Affected if Custom roles exist or have been configured in the system - the vulnerability is only exploitable when custom role functionality is enabled
  3. Review role-based access control configuration
    Inspect the authorization settings for custom roles to determine if object-level access controls are properly enforced. Check the role permissions matrix or configuration files for whether explicit object-level validation is configured
    Affected if Object-level authorization checks are missing or not explicitly configured for custom role operations - this indicates the vulnerable condition exists
  4. Audit user-to-role assignments
    Review which users are assigned to custom roles, particularly any users with elevated or non-standard role assignments that could be exploited through IDOR manipulation
    Affected if Users are assigned to custom roles and those roles interact with objects/resources that may lack proper authorization validation

A user is affected if running Projectopia version 5.1.25.2 or earlier AND custom role functionality is enabled, as the IDOR vulnerability allows manipulation of object references in role-based operations.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Projectopia beyond 5.1.25.2; if no patch is available, implement proper object-level authorization checks on all custom role operations and validate that the requesting user has explicit permission to access the referenced object.

Recommended fix Moderate confidence

Projectopia version 5.1.25.3 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Projectopia in the plugin list
  4. Check if an update is available for Projectopia
  5. If an update is available, click 'Update Now' to update to the latest version
  6. Verify the update was successful by checking the plugin version
  7. Ensure the updated version is higher than 5.1.25.2 (e.g., 5.1.25.3 or later)
  8. Test that custom role functionality works correctly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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