dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-39350

HIGH · 8.2 CVSS v3.1 Published 2025-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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
Missing Authorization vulnerability in Rocket Apps wProject.This issue affects wProject: from n/a before 5.8.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 confidence

Missing Authorization vulnerability in Rocket Apps wProject allows unauthenticated or unauthorized users to access functionality they should not have access to. The vulnerability exists in versions prior to 5.8.0, with a CVSS score of 8.2 indicating significant impact likely involving exposure of sensitive project data or administrative functions.

MitigationUpgrade to wProject version 5.8.0 or later to obtain the authorization fix. If immediate upgrading is not possible, review access controls and restrict exposure of the wProject application to untrusted networks.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 if wProject is installed
    Check your web server for the presence of wProject application files or look for wProject-related processes/services
    Affected if wProject application is present on the system
  2. Determine the installed wProject version
    Check the application version information typically found in the admin panel under 'About' or 'System Info', or inspect version files in the application root directory if accessible
    Affected if The installed version cannot be determined or is visible
  3. Compare version against the fixed release
    Compare your installed version number to 5.8.0 - the version where the vulnerability is patched
    Affected if The installed version is below 5.8.0 (for example, 5.7.x, 5.6.x, or earlier)
  4. Review application access control logs
    Examine application audit logs or access logs for any unexpected user actions or privilege escalation patterns, particularly actions performed by users without expected permissions
    Affected if Logs show unauthorized access attempts or actions performed by users lacking proper permissions

A user is affected if wProject is installed and the installed version is below 5.8.0, or if logs show evidence of unauthorized access due to missing authorization checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to wProject version 5.8.0 or later to obtain the authorization fix. If immediate upgrading is not possible, review access controls and restrict exposure of the wProject application to untrusted networks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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