docjojo atec Debug Plugin up to 1.2.22 on WordPress debug_path absolute path traversal

Summaryinfo

A vulnerability, which was classified as problematic, has been found in docjojo atec Debug Plugin up to 1.2.22 on WordPress. The affected element is an unknown function. Performing a manipulation of the argument debug_path results in absolute path traversal. This vulnerability is cataloged as CVE-2025-9518. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in docjojo atec Debug Plugin up to 1.2.22 on WordPress. It has been classified as problematic. This affects an unknown functionality. The manipulation of the argument debug_path with an unknown input leads to a absolute path traversal vulnerability. CWE is classifying the issue as CWE-36. The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize absolute path sequences such as "/abs/path" that can resolve to a location that is outside of that directory. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

The atec Debug plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation on the 'debug_path' parameter in all versions up to, and including, 1.2.22. This makes it possible for authenticated attackers, with Administrator-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

The weakness was shared by Jonas Benjamin Friedli. The advisory is shared at wordfence.com. This vulnerability is uniquely identified as CVE-2025-9518 since 08/27/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Additional levels of successful authentication are needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• docjojo

Name

• atec Debug Plugin

Version

• 1.2.0
• 1.2.1
• 1.2.2
• 1.2.3
• 1.2.4
• 1.2.5
• 1.2.6
• 1.2.7
• 1.2.8
• 1.2.9
• 1.2.10
• 1.2.11
• 1.2.12
• 1.2.13
• 1.2.14
• 1.2.15
• 1.2.16
• 1.2.17
• 1.2.18
• 1.2.19
• 1.2.20
• 1.2.21
• 1.2.22

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion