Frontend User Notes <= 2.1.0 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary Note Modification
Strategic Overview
- Status
- Patched in 2.1.1
- Affected Plugin
- Frontend User Notes
- Affected Version
<= 2.1.0- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2025-12071
At a glance
CVE-2025-12071 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Frontend User Notes WordPress plugin, affecting versions <= 2.1.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.1.1; sites on affected versions should update now. Disclosed February 2026, reported by Athiwat Tiprasaharn (Jitlada).
Vulnerability Overview
The Frontend User Notes plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.1.0 via the 'funp_ajax_modify_notes' AJAX endpoint due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify arbitrary notes that do not belong to them.
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-639: Authorization Bypass Through User-Controlled Key
Frontend User Notes <= 2.1.0 carries this weakness at funp_ajax_modify_notes, and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Frontend User Notes the fix is 2.1.1: builds <= 2.1.0 are affected, anything from 2.1.1 onward is not.
Remediation
Update to version 2.1.1, or a newer patched version
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. None of that substitutes for the fix: Frontend User Notes 2.1.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Frontend User Notes
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C