CVE-2025-62973

BuddyForms <= 2.9.0 - Missing Authorization

2025-10-19 00:00
Nabil Irawan

Strategic Overview

Status
Unpatched
Affected Plugin
Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC)
Affected Version
<= 2.9.0
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-62973
View all Post Form – Registration Form – Profile Form for User Profiles – Frontend Content Forms for User Submissions (UGC) vulnerabilities

At a glance

CVE-2025-62973 is a medium-severity Missing Authorization vulnerability in the Post Form WordPress plugin, affecting versions <= 2.9.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed October 2025, reported by Nabil Irawan.

Vulnerability Overview

The BuddyForms plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in versions up to, and including, 2.9.0. This makes it possible for unauthenticated attackers to perform an unauthorized action.

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 privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Post Form <= 2.9.0 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. No fixed build of this plugin is recorded for Post Form yet, so installs running <= 2.9.0 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?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-62973https://www.wordfence.com/threat-intel/vulnerabilities/id/c84cf8f1-ff13-47e9-bf9d-a6f638af0492https://nvd.nist.gov/vuln/detail/CVE-2025-62973

Related records

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