CVE-2025-32205

Piotnet Forms <= 1.0.30 - Authenticated (Editor+) Path Traversal

2025-04-07 00:00
Trương Hữu Phúc (truonghuuphuc)

Strategic Overview

Status
Unpatched
Affected Plugin
Piotnet Forms
Affected Version
<= 1.0.30
CVSS
3.8Low
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2025-32205
View all Piotnet Forms vulnerabilities

At a glance

CVE-2025-32205 is a low-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Piotnet Forms WordPress plugin, affecting versions <= 1.0.30. It carries a CVSS score of 3.8 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Editor level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed April 2025, reported by Trương Hữu Phúc (truonghuuphuc).

Vulnerability Overview

The Piotnet Forms plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.0.30. This makes it possible for authenticated attackers, with Editor-level access and above, to perform actions on files outside of the originally intended directory.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in Piotnet Forms <= 1.0.30 takes an account at Editor level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. No fixed build of this plugin is recorded for Piotnet Forms yet, so installs running <= 1.0.30 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

An attacker needs Editor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-32205https://www.wordfence.com/threat-intel/vulnerabilities/id/eb0892fd-b5dd-4dc8-bc45-41c05f1c03cfhttps://nvd.nist.gov/vuln/detail/CVE-2025-32205

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C