LiveActive security incident?Get immediate response
CVE Record

CVE-2021-4378: WP Quick FrontEnd Editor <= 5.5 - Authenticated (Subscriber+) Stored Cross-Site Scripting

The WP Quick FrontEnd Editor plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 5.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with minimal permissions like subscribers, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A low-privileged WordPress user could store malicious script content through WP Quick FrontEnd Editor. That script would run for later visitors to the affected page, potentially exposing user data or changing page behavior. This is most concerning on sites allowing public registration or many subscriber accounts.

Executive priority

Treat as a moderate priority. It is not documented as actively exploited here, but affected public or membership WordPress sites should respond promptly because low-privileged accounts can create persistent browser-side risk.

Technical view

CVE-2021-4378 is stored cross-site scripting in WP Quick FrontEnd Editor versions up to and including 5.5. The issue is insufficient input sanitization and output escaping. Authenticated attackers with subscriber-level access can inject scripts that execute when an injected page is viewed.

Likely exposure

Exposure is limited to WordPress sites running WP Quick FrontEnd Editor <= 5.5 with authenticated users, especially subscriber-level accounts. Sites without the plugin, without affected versions, or without low-privileged user access are less likely exposed.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires an authenticated account but only minimal privileges. Stored XSS can become business-relevant if administrators or customers view affected content.

Researcher notes

Evidence supports authenticated subscriber-plus stored XSS, CWE-79, CVSS 6.4. The provided data does not confirm a patched version or active exploitation. Avoid assuming broader WordPress core exposure; this is plugin-specific.

Mitigation direction

  • Inventory WordPress sites for WP Quick FrontEnd Editor and installed version.
  • Disable or remove affected versions until vendor guidance confirms a safe release.
  • Restrict public registration and remove unnecessary subscriber accounts.
  • Limit front-end editing access to trusted roles only.
  • Review Wordfence, Nintechnet, and vendor guidance for confirmed fixes.

Validation and detection

  • Check WordPress plugin inventory for WP Quick FrontEnd Editor <= 5.5.
  • Confirm whether subscriber-level users can access front-end editing features.
  • Review affected pages for unexpected script content or suspicious edits.
  • Inspect WordPress audit logs for edits by low-privileged accounts.
  • Verify mitigation blocks low-privileged users from modifying rendered page content.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-4378 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2021-4378Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
labibahmed42WP Quick FrontEnd Editor – WordPress Plugin0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.