FKIE_CVE-2026-1867

Vulnerability from fkie_nvd - Published: 2026-03-11 06:17 - Updated: 2026-03-11 14:16
Severity ?
5.9 (Medium) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Summary
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.
References
contact@wpscan.comhttps://wpscan.com/vulnerability/a78ebcd2-9355-4f4e-829e-b10867463576/
Impacted products
Vendor Product Version
To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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\u0027s settings, it is possible for an unauthenticated attacker to export and download all of the form data/settings, including the administrator\u0027s email address."
    },
    {
      "lang": "es",
      "value": "El plugin de WordPress Guest posting / Frontend Posting / Front Editor anterior a la versi\u00f3n 5.0.6 permite pasar un par\u00e1metro URL para regenerar un archivo .json basado en datos de demostraci\u00f3n que crea inicialmente. Si un administrador modifica el formulario de demostraci\u00f3n y habilita las notificaciones de administrador en la configuraci\u00f3n del plugin de WordPress Guest posting / Frontend Posting / Front Editor anterior a la versi\u00f3n 5.0.6, es posible que un atacante no autenticado exporte y descargue todos los datos/ajustes del formulario, incluida la direcci\u00f3n de correo electr\u00f3nico del administrador."
    }
  ],
  "id": "CVE-2026-1867",
  "lastModified": "2026-03-11T14:16:17.450",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.9,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.2,
        "impactScore": 3.6,
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-03-11T06:17:13.397",
  "references": [
    {
      "source": "contact@wpscan.com",
      "url": "https://wpscan.com/vulnerability/a78ebcd2-9355-4f4e-829e-b10867463576/"
    }
  ],
  "sourceIdentifier": "contact@wpscan.com",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-200"
        }
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.