Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-6549: CWE-200 Information Exposure in coffee2code Admin Post Navigation

0
Medium
VulnerabilityCVE-2024-6549cvecve-2024-6549cwe-200
Published: Sat Jul 27 2024 (07/27/2024, 01:51:05 UTC)
Source: CVE Database V5
Vendor/Project: coffee2code
Product: Admin Post Navigation

Description

CVE-2024-6549 is a medium severity vulnerability in the WordPress plugin Admin Post Navigation by coffee2code. It allows unauthenticated attackers to retrieve the full filesystem path of the web application due to leftover test files with display_errors enabled. This full path disclosure does not directly compromise confidentiality, integrity, or availability but can aid attackers in crafting further attacks if combined with other vulnerabilities. The vulnerability affects all versions up to and including 2. 1. No known exploits are currently reported in the wild. The vulnerability requires no authentication or user interaction and has a CVSS score of 5. 3. Organizations using this plugin should update or mitigate exposure to prevent information leakage that could facilitate more severe attacks.

AI-Powered Analysis

AILast updated: 02/26/2026, 03:13:44 UTC

Technical Analysis

CVE-2024-6549 is an information disclosure vulnerability classified under CWE-200 affecting the Admin Post Navigation WordPress plugin developed by coffee2code. The root cause is the presence of test files left in the plugin that have PHP's display_errors directive enabled, which reveals the full filesystem path of the web server hosting the WordPress site. This vulnerability exists in all plugin versions up to and including 2.1. An unauthenticated attacker can trigger error messages that disclose the absolute path to the web application directory. While the disclosed information alone does not allow direct compromise, it can be leveraged to facilitate other attacks such as local file inclusion, path traversal, or targeted exploitation of other vulnerabilities by providing attackers with precise directory structure knowledge. The vulnerability does not impact integrity or availability directly and requires no privileges or user interaction to exploit. No public exploits have been reported yet, but the presence of this information leakage increases the attack surface and risk for affected sites. The CVSS 3.1 base score is 5.3, reflecting a medium severity level due to the ease of exploitation and the limited impact of the disclosed information alone.

Potential Impact

The primary impact of CVE-2024-6549 is the exposure of sensitive internal information about the web server's directory structure. This information can significantly aid attackers in crafting more effective attacks, such as local file inclusion, remote code execution, or privilege escalation, especially if other vulnerabilities exist on the same system. Organizations running the vulnerable plugin may face increased risk of targeted attacks and exploitation chains. Although the vulnerability itself does not allow direct compromise, it lowers the barrier for attackers to identify and exploit other weaknesses. This can lead to data breaches, website defacement, or service disruption if combined with additional vulnerabilities. The impact is particularly relevant for websites with sensitive data or critical business functions relying on WordPress and this plugin.

Mitigation Recommendations

To mitigate CVE-2024-6549, organizations should immediately update the Admin Post Navigation plugin to a version where this issue is fixed once available. Until a patch is released, administrators should manually remove or disable any test files that enable display_errors or other debugging features within the plugin directory. Additionally, configuring the PHP environment to disable display_errors on production servers is critical to prevent information leakage. Web application firewalls (WAFs) can be configured to block requests that trigger error messages or access test files. Regular security audits and vulnerability scanning should be performed to detect such information disclosures. Monitoring logs for suspicious requests targeting plugin files can help identify exploitation attempts. Finally, reducing the attack surface by limiting plugin usage to only necessary components and following WordPress security best practices will help mitigate risk.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2024-07-08T14:00:13.429Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6c06b7ef31ef0b55f1a3

Added to database: 2/25/2026, 9:39:18 PM

Last enriched: 2/26/2026, 3:13:44 AM

Last updated: 2/26/2026, 11:16:33 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats