dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-10737

HIGH · 7.5 CVSS v3.1 Published 2026-06-04
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
The SP Project & Document Manager plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the view_file function in all versions up to, and including, 4.71. This makes it possible for unauthenticated attackers to read file metadata and obtain download links for arbitrary files stored inside project folders on the server, which can contain sensitive information. The authorization gate uses a negated nonce check OR-chained with permission checks, meaning a missing or invalid nonce causes the entire condition to evaluate to true and bypass all preceding capability and ownership checks. The secondary fallback check only denies access for root-level files (pid == 0), leaving all files stored inside project folders fully exposed to unauthenticated users who supply only a valid file ID in a POST request to admin-ajax.php.

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

The SP Project & Document Manager plugin for WordPress has a broken access control vulnerability in the view_file function. The authorization logic uses a negated nonce check OR-chained with permission checks, causing missing/invalid nonces to evaluate the entire condition as true and bypass capability checks. A secondary fallback only denies access for root-level files (pid == 0), leaving all files in project folders accessible to unauthenticated users via POST requests to admin-ajax.php with a valid file ID.

MitigationUpgrade to version 4.72 or later which implements proper capability checks. Until then, consider restricting admin-ajax.php access or disabling the plugin.

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. Confirm plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and find 'SP Project & Document Manager', or inspect the plugin header file (sp-project-manager.php) for the 'Version' field.
    Affected if The installed version is lower than 4.72 (the patched version).
  2. Verify WordPress site responds to admin-ajax.php
    Send a GET or POST request to /wp-admin/admin-ajax.php?action=sp_project_sm without providing any authentication cookies or nonce tokens.
    Affected if The site returns a successful HTTP response (200) rather than a 401/403 error, indicating the endpoint is accessible to unauthenticated users.
  3. Test unauthorized file metadata disclosure
    Send a request to admin-ajax.php with action=sp_project_sm and a file parameter (such as 'view_file' or 'pid' values pointing to existing project files) without valid authentication or nonce.
    Affected if The response contains file metadata (file names, paths, download URLs) for files the user should not have access to, indicating the authorization bypass is present.
  4. Check plugin configuration for public access settings
    Review the plugin settings under SP Project > Settings in the WordPress admin, specifically looking for any option that enables public/unauthenticated file access.
    Affected if Public access is enabled or the 'Allow guest download' setting is active without proper capability enforcement.

A user is affected if the SP Project & Document Manager plugin version is below 4.72 AND the admin-ajax.php endpoint responds to unauthenticated requests with file metadata or download links.

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 version 4.72 or later which implements proper capability checks. Until then, consider restricting admin-ajax.php access or disabling the plugin.

Recommended fix High confidence

SP Project & Document Manager version 4.72 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'SP Project & Document Manager' in the plugin list
  4. Check the current installed version - if it is 4.71 or below, an update is required
  5. Navigate to Plugins > Add New > Upload Plugin (or check for updates directly)
  6. Update the plugin to the latest available version (4.72 or higher)
  7. Verify the update was successful by confirming the new version number
  8. Test that the view_file functionality works correctly for authenticated users with proper permissions
Caveat Review plugin settings and custom configurations after upgrade, as minor version updates may include functionality changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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