dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-1867

MEDIUM · 5.9 CVSS v3.1 Published 2026-03-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an unauthenticated information disclosure vulnerability in the Guest posting / Frontend Posting / Front Editor WordPress plugin. An unauthenticated attacker can exploit a URL parameter to force regeneration of a .json file containing sensitive form data and settings, including administrator email addresses when admin notifications are enabled. The vulnerability exists in versions before 5.0.6.

MitigationUpdate the WordPress plugin to version 5.0.6 or later to remediate this vulnerability. Until patched, consider disabling admin notifications in the plugin settings to reduce exposure of administrator email addresses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for folders containing 'guest-posting', 'frontend-posting', or 'front-editor'. Alternatively, log into WordPress admin and navigate to Plugins to list installed plugins.
    Affected if The plugin with any of these names is present in the WordPress installation
  2. Check the installed plugin version
    If the plugin is found, open its main PHP file or readme.txt and locate the version declaration. Compare this version number to the affected range (anything below 5.0.6).
    Affected if The installed version is below 5.0.6
  3. Verify admin notifications are enabled
    Access the plugin settings through WordPress admin (usually under Settings or the plugin's own menu). Look for a notification setting that involves administrator email alerts. Check if this setting is turned on or configured.
    Affected if Admin notifications are enabled in the plugin configuration (this increases exposure of admin email addresses)
  4. Check for exposed .json file
    Attempt to access the suspected .json endpoint. Common paths may include the plugin's directory or a designated upload/cache folder. Use a web browser or curl to request the URL and observe if sensitive form data or settings (including email addresses) are returned in JSON format.
    Affected if A .json file is accessible and contains sensitive form data or admin email addresses

You are affected if the plugin is installed with a version below 5.0.6 and the vulnerable .json endpoint is accessible, with higher severity when admin notifications are enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WordPress plugin to version 5.0.6 or later to remediate this vulnerability. Until patched, consider disabling admin notifications in the plugin settings to reduce exposure of administrator email addresses.

Recommended fix High confidence

5.0.6

  1. 1. Log in to the WordPress admin dashboard as an administrator
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Guest posting / Frontend Posting / Front Editor' plugin
  4. 4. If the plugin shows a version lower than 5.0.6, click 'Update Now' to upgrade to version 5.0.6
  5. 5. Alternatively, download version 5.0.6 from the WordPress Plugin Repository and upload it manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin version shows 5.0.6 or higher
  7. 7. Test that the frontend posting functionality works correctly after the upgrade
  8. 8. Review plugin settings to ensure configuration is as expected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1867 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1867 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data