S4E just found a critical-severity finding from cve-2017-7504 scanner
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
low·Product Based Web Vulnerabilities·Updated Dec 13, 2025

WordPress ManageWP Worker Full Path Disclosure Scanner

Detects 'Full Path Disclosure' vulnerability in WordPress ManageWP Worker.

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsurl
CostFree
3.2k
Times Used
continuous scan runs
5.9k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
Detail

WordPress is a widely used content management system (CMS) that powers a significant portion of websites on the internet. It is utilized by individuals, bloggers, small businesses, and large organizations for creating and managing websites. The platform's flexibility and wide range of plugins allow users to expand its functionality and tailor it to specific needs. Plugins like ManageWP Worker help streamline website management tasks such as backups, updates, and monitoring from a single dashboard. These extensions enhance WordPress's capabilities, making it a preferred choice for web developers and administrators. The ease of use, scalability, and community support contribute to WordPress's popularity as a comprehensive website solution.

Full Path Disclosure (FPD) is a web security vulnerability that exposes the internal server path of a vulnerable application or server. In this context, the WordPress ManageWP Worker plugin allows access to specific files without proper access controls. This oversight can lead to the exposure of sensitive server path information through error messages. Attackers can exploit this information to gain insights into the server's directory structure, which can assist in targeted attacks. Addressing FPD vulnerabilities is essential to prevent unauthorized access and data exposure. The vulnerability arises due to improper error handling and insufficient access restrictions on plugin files.

The vulnerability in the ManageWP Worker involves accessing certain plugin files, specifically within the "/wp-content/plugins/worker/src/MMB/User.php" path. These files provide detailed PHP error messages when accessed directly without ABSPATH protection. The error messages reveal the full path of the server's directory where the files are located. The vulnerability is validated if a status code 200 is returned, and the response body contains indicators like "Fatal error," "Uncaught Error," and the directory path "/plugins/worker/". This specific endpoint and the inadequate protection mechanisms are the focal points of exploitation. Addressing such vulnerabilities requires scrutinizing the access policies for plugin files.

Exploitation of the Full Path Disclosure vulnerability may lead to information leakage that could assist potential attackers in mapping the server's file system. This information can help in conducting further attacks, such as exploiting other vulnerabilities that require knowledge of the directory structure. Although this vulnerability does not directly allow unauthorized access or code execution, it serves as a stepping stone for more sophisticated attacks. Information gathered through FPD can enable attackers to craft precise attacks targeting known security weaknesses within the disclosed paths. Protecting sensitive paths and adopting secure error-handling practices are vital in mitigating this threat.

REFERENCES

Solution Advice
  • Ensure that ABSPATH protection is enabled for all plugin files.
  • Implement error handling that conceals sensitive server path information from unauthorized users.
  • Regularly update the WordPress core and plugins to benefit from security patches.
  • Conduct security audits to identify and rectify similar vulnerabilities across the website.
  • Restrict direct access to plugin files through proper server configuration.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.