sales@hackhalt.com
Free Download

Home / Threats / CVE-2026-84069

WebFacing™ - Security Vulnerability (CVE-2026-84069)

CVE-2026-84069

Vulnerability CVE-2026-84069 PLUGIN webfacing MEDIUM

The WebFacing™ WordPress plugin before 5.4 does not restrict access to one of its bundled scripts and does not validate a user-supplied path before using it to include a local file, allowing unauthenticated users to perform Local File Inclusion.

CVE-2026-84069

MEDIUM CVSS 5.3 Published 2026-09-27 Updated 2026-09-28
AI Risk Moderate (52/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P4 Planned
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Affected Components 1
Reference Links 1
AI Risk Engine Moderate (52/100)
Exploitability Low
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-09-27 CVE published and first recorded in the threat feed.
  2. 2026-09-28 Record updated with latest vulnerability metadata.
  3. 2026-10-01 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 8 days ago

AI enriched 8 days ago (2026-10-01 01:43 UTC)

Technical Summary

The WebFacing™ WordPress plugin before 5.4 does not restrict access to one of its bundled scripts and does not validate a user-supplied path before using it to include a local file, allowing unauthenticated users to perform Local File Inclusion.

Potential Impact

Severity is MEDIUM (CVSS 5.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Low based on low-bar exploit prerequisites.

Primary risk drivers: low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 52/100 (Moderate, Low) with priority P4 Planned. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

WebFacing™ PLUGIN · webfacing Affected: >= 5.3, < 5.4 Fixed in: 5.4

Related Vulnerabilities

Browse All Threats

Newest linked vulnerabilities to keep visitors exploring adjacent CVE coverage.

No related vulnerability records were found yet for this context.

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update WebFacing™ to 5.4 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs WebFacing™, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs WebFacing™. Versions below 5.4 are vulnerable; that release and later are not. No account is needed to exploit this, so a public site is reachable by anyone.

How do I fix it?

Update WebFacing™ to version 5.4 or later. That is the complete fix. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Path Traversal flaw. An attacker who exploits it can read files outside the intended directory, including wp-config.php.

WordPress security that blocks attacks before they land.

sales@hackhalt.com

Product

Resources

Company

© Hack Halt Inc. All rights reserved.