dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-31118

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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 Smartypants SP Project & Document Manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects SP Project & Document Manager: from n/a through 4.70.

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 Smartypants SP Project & Document Manager allows attackers to bypass access control security levels. The plugin has incorrectly configured access controls that permit unauthorized users to access project documents or functionality they should not have permission to view or modify.

MitigationUpdate SP Project & Document Manager to a version beyond 4.70 that includes proper authorization enforcement, or apply vendor-provided security patches. Review and properly configure all access control security levels in the meantime.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

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
    Navigate to WordPress admin > Plugins and locate 'SP Project & Document Manager' in the list of installed plugins. Note the version number displayed next to the plugin name.
    Affected if Plugin is installed and version is 4.70 or lower
  2. Check plugin version
    In WordPress admin, go to Plugins > Installed Plugins > SP Project & Document Manager. Compare the displayed version number against version 4.70. The plugin version is typically shown in the plugin description area or can be checked via FTP in the main plugin file header.
    Affected if Installed version is 4.70 or lower (vulnerable versions)
  3. Review access control security levels
    Access the plugin settings in WordPress admin (typically under Settings > SP Document Manager or a dedicated SP menu). Locate the access control or security level configuration panel. Verify which user roles (Administrator, Editor, Author, Subscriber, etc.) have access to which project documents or management functions.
    Affected if Security levels are set to allow lower-privileged users (like Subscribers or Authors) to access or modify documents they should not have permission to access, or if no role-based restrictions are visible in the settings
  4. Test unauthorized access capability
    Log in as a low-privilege user (e.g., Subscriber or Author) and attempt to access project documents or management features that should be restricted to Administrators or higher roles. Try accessing the SP Document Manager admin pages directly or viewing documents assigned to higher-level users.
    Affected if A low-privilege user can view, modify, or delete project documents or access admin-level functionality they should not be able to access
  5. Inspect user role configuration
    Go to the plugin's user role or permission settings page. Examine which capabilities are assigned to each WordPress role. Check if non-administrative roles have been granted sensitive capabilities such as 'manage_options', 'delete_others_posts', or full document access.
    Affected if Non-administrator roles have elevated capabilities that bypass proper authorization checks

If the SP Project & Document Manager plugin is installed with version 4.70 or lower and the access control settings allow lower-privileged users to access or modify documents beyond their intended permissions, the environment is affected by this authorization bypass vulnerability.

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

Update SP Project & Document Manager to a version beyond 4.70 that includes proper authorization enforcement, or apply vendor-provided security patches. Review and properly configure all access control security levels in the meantime.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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