dbcve.org
DirectorypressWordPress extension · Designinvento

CVE-2023-37967

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-13
Fix available
A fix is available. Upgrade to 3.6.4 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
Missing Authorization vulnerability in Designinvento DirectoryPress allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects DirectoryPress: from n/a through 3.6.2.

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

DirectoryPress plugin versions through 3.6.2 contain a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This broken access control likely enables unauthenticated users to access sensitive administrative functions or data they should not have permission to view or modify.

MitigationImplement proper role-based access control (RBAC) checks and authorization validation on all sensitive functions and resources to ensure users can only access permitted 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
DirectorypressWordPress extension
Affected:< 3.6.4

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Verify DirectoryPress plugin installation
    Check for the DirectoryPress plugin in your WordPress installation at wp-content/plugins/designinvento-directorypress/ or search for 'DirectoryPress' in the WordPress plugins admin panel
    Affected if The plugin is not found in the expected locations
  2. Identify installed DirectoryPress version
    Read the version from the main plugin file (typically directorypress.php) or check the plugin details in WordPress admin under Plugins > Installed Plugins
    Affected if The version number is less than 3.6.4 (e.g., 3.6.2, 3.6.1, 3.6.0, or any version before 3.6.4)
  3. Inspect access control configuration
    Check WordPress user role capabilities and DirectoryPress-specific security settings in the plugin configuration panel at DirectoryPress > Settings > Security or Access Control
    Affected if Public access is enabled for administrative functions or sensitive endpoints are accessible without authentication
  4. Test for unauthorized admin function access
    Attempt to access DirectoryPress admin URLs (such as wp-admin/admin.php?page=directorypress_) while logged out or as a subscriber-level user to verify if authorization is enforced
    Affected if Administrative pages or sensitive data loads without requiring proper admin-level authentication

If DirectoryPress version is below 3.6.4 and administrative functions are accessible without proper authentication, the environment is affected by this CVE.

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 3.6.4 or later
Fixed in 3.6.4
Interim mitigation

Implement proper role-based access control (RBAC) checks and authorization validation on all sensitive functions and resources to ensure users can only access permitted functionality.

Recommended fix Moderate confidence

DirectoryPress 3.6.4 or later

  1. Backup the entire DirectoryPress/WordPress installation including database
  2. Verify current DirectoryPress version is below 3.6.4
  3. Download DirectoryPress version 3.6.4 or later from the official source (Designinvento/CodeCanyon)
  4. Update the plugin via WordPress admin dashboard or replace files via FTP/SFTP
  5. Clear any caches if caching plugins are used
  6. Verify the new version is installed (should show 3.6.4 or higher)
  7. Test that administrative functions and access controls work correctly
Caveat Review plugin changelog for any breaking changes between your current version and 3.6.4 before upgrading; test in staging environment first if possible

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

Fix this in Directorypress Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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