Radar sectionsDatabase
Check my site
WordPress plugin

Front User Submit | Front Editor <= 3.7.0 — Authenticated (Subscriber+) Stored Cross-Site Scripting

f34722fb-e852-4194-b839-7d885d212fc9Published · Updated

Action summary

Affected: <3.8.0Update to 3.8.0 or newer

All remediation steps
Severity
Medium6.4
CVSS
6.4
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:C Scope
Changed
C:L Confidentiality
Low
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-79 Cross-Site Scripting
Required access
Unknown
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Guest posting / Frontend Posting / Front Editor – WP Front User Submit front-editor

  1. Affected< 3.8.0
  2. Patched in3.8.0

Update to 3.8.0 or newer.

You are affected if you run < 3.8.0. Version 3.8.0 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Guest posting / Frontend Posting / Front Editor – WP Front User Submit.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 3.8.0, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Guest posting / Frontend Posting / Front Editor – WP Front User Submit to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence.

The Front User Submit | Front Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘formBuilderData’ parameter saved through the save_post_front_settings() function called via AJAX in versions up to, and including, 3.7.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Guest posting / Frontend Posting / Front Editor – WP Front User Submit

All 12
More vulnerabilities in Guest posting / Frontend Posting / Front Editor – WP Front User Submit
SeverityVulnerabilityCVEPublished
Medium5.3Unauthenticated Information Exposure
<5.0.6Update to 5.0.6
CVE-2026-1867
Medium5.3Missing Authorization to Unauthenticated Media Deletion
≤5.0.0Update to 5.0.1
CVE-2025-13419
Medium4.7Open Redirect
≤4.9.5Update to 5.0.0
CVE-2025-12569
Medium6.1Reflected Cross-Site Scripting
≤4.9.3Update to 4.9.4
CVE-2025-28988
Medium4.3Cross-Site Request Forgery
≤4.9.4No patch available
CVE-2025-52795

Same weakness (Cross-Site Scripting)

All Cross-Site Scripting
Other Cross-Site Scripting vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity medium, CVSS 6.4

  2. Record last updated

Sources & licenses

Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?