dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-6570

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 Glossary plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 2.2.26. This is due the plugin utilizing wpdesk and not preventing direct access to the test files along with display_errors being enabled. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

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 Glossary plugin for WordPress up to version 2.2.26 is vulnerable to Full Path Disclosure. The plugin includes test files from the wpdesk library that can be accessed directly by unauthenticated users. When PHP's display_errors setting is enabled on the server, these files output the full filesystem path of the web application, which can aid attackers in reconnaissance for more severe exploits.

MitigationUpdate the Glossary plugin to the latest version and disable display_errors in php.ini or the server configuration to prevent PHP error messages from revealing path information.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Check Glossary plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the Glossary plugin to view its version number, or inspect the plugin header comment in wp-content/plugins/glossary/includes/glossary.php
    Affected if Version is 2.2.26 or lower
  2. Locate wpdesk test files in plugin directory
    Search the plugin directory for wpdesk-related subdirectories, typically found at wp-content/plugins/glossary/lib/wpdesk-lib/ or similar paths containing test or example files from the wpdesk library
    Affected if Test files from wpdesk library exist in the plugin directory
  3. Verify test file web accessibility
    Attempt to directly access potential test file URLs (such as /wp-content/plugins/glossary/lib/wpdesk-lib/ or any .php files within wpdesk subdirectories) using a web browser or curl request without authentication
    Affected if Test files are directly accessible via HTTP without authentication
  4. Check PHP display_errors setting
    Review php.ini or create a temporary PHPinfo file to confirm whether display_errors is set to On; also check .htaccess or server vhost configuration for any display_errors directives
    Affected if display_errors is enabled (On) in PHP configuration

Environment is affected if Glossary plugin version is 2.2.26 or lower, wpdesk test files are publicly accessible via web, and PHP display_errors is enabled, allowing unauthenticated users to trigger full path disclosure.

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

Update the Glossary plugin to the latest version and disable display_errors in php.ini or the server configuration to prevent PHP error messages from revealing path information.

Recommended fix Moderate confidence
  1. 1. Access your server's php.ini configuration file (or create/edit a php.ini in the web root if none exists)
  2. 2. Locate or add the directive: display_errors = Off
  3. 3. If using .htaccess (Apache), add: php_flag display_errors Off
  4. 4. If using FastCGI Process Manager (FPM), restart PHP-FPM: sudo systemctl restart php-fpm
  5. 5. Restart Apache or nginx to apply changes: sudo systemctl restart apache2 (or sudo systemctl restart nginx)
  6. 6. Verify the setting is active by checking phpinfo() or creating a test script that outputs an error

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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