VulnerabilityPublished 11 Mar 2026

CVE-2026-1867: Guest posting / Frontend Posting / Front Editor (WordPress plugin) · Information Exposure

Affects Guest posting / Frontend Posting / Front Editor (WordPress plugin)Source CVE Database V5

Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 5.0.6 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.0.6

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Guest posting / Frontend Posting / Front Editor (WordPress plugin) to 5.0.6.

Affected software

Product	Affected	Fixed in
Guest posting / Frontend Posting / Front Editor	Affected <5.0.6	Fixed in 5.0.6

AI-suggested

Immediate mitigation should focus on restricting access to the vulnerable plugin functionality by implementing web application firewall (WAF) rules that block requests containing the specific URL parameter used to regenerate the .json file.
Disable or restrict the Guest posting / Frontend Posting / Front Editor plugin if it is not essential to site operations until a patched version is released.
Monitor web server logs for suspicious requests targeting the .json regeneration endpoint to detect potential exploitation attempts.
Limit administrative privileges and avoid enabling admin notifications in the plugin settings unless necessary.
Once available, promptly update the plugin to version 5.0.6 or later that addresses this vulnerability.
Consider implementing additional access controls such as IP whitelisting or authentication requirements for accessing sensitive plugin features.
Educate site administrators about phishing risks stemming from exposed email addresses and encourage use of multifactor authentication to protect accounts.
Regularly audit WordPress plugins for security updates and vulnerabilities to maintain a secure environment. These steps go beyond generic advice by focusing on immediate access restriction, monitoring, and administrative best practices tailored to this specific vulnerability.

Description

The Guest posting / Frontend Posting / Front Editor WordPress plugin before 5.0.6 allows passing a URL parameter to regenerate a .json file based on demo data that it initially creates. If an administrator modifies the demo form and enables admin notifications in the Guest posting / Frontend Posting / Front Editor WordPress plugin before 5.0.6's settings, it is possible for an unauthenticated attacker to export and download all of the form data/settings, including the administrator's email address.

Impact

The primary impact of CVE-2026-1867 is the unauthorized disclosure of sensitive configuration data, including administrator email addresses, from WordPress sites using the vulnerable plugin. This information exposure can lead to targeted phishing attacks, social engineering, and reconnaissance activities by attackers. While the vulnerability does not directly allow code execution or site takeover, the leaked data can be a stepping stone for more severe attacks. Organizations relying on this plugin risk compromise of administrator accounts or increased attack surface due to exposed contact information. The vulnerability affects confidentiality and potentially integrity if attackers leverage the information to gain further access. Because exploitation requires no authentication or user interaction, the threat is accessible to any remote attacker scanning for vulnerable sites. The scope includes all WordPress sites running the affected plugin versions, which can be substantial given WordPress's global popularity. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future attacks. Overall, the impact is significant for organizations that value the privacy of their administrative contacts and the security posture of their WordPress deployments.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/a78ebcd2-9355-4f4e-829e-b10867463576/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Mar 2026, 06:29 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats