Front End PM <= 11.4.6 - Authenticated (Subscriber+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 11.4.7
- Affected Plugin
- Front End PM
- Affected Version
<= 11.4.6- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-39788
At a glance
CVE-2026-39788 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Front End PM WordPress plugin, affecting versions <= 11.4.6. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 11.4.7; sites on affected versions should update now. Disclosed October 2026, reported by Ananda Dhakal.
Vulnerability Overview
The Front End PM plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 11.4.6. This is due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Front End PM <= 11.4.6 takes an account at Subscriber level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Front End PM the fix is 11.4.7: builds <= 11.4.6 are affected, anything from 11.4.7 onward is not.
Remediation
Update to version 11.4.7, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber 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. None of that substitutes for the fix: Front End PM 11.4.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C