CVE-2025-23566

WordPress Custom Post plugin <= 1.0 - CSRF to Stored XSS vulnerability

Published Jan 16, 2025 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
Description
Cross-Site Request Forgery (CSRF) vulnerability in syedamirhussain91 Custom Post custom-post-type-gui allows Stored XSS.This issue affects Custom Post: from n/a through <= 1.0.

Analysis

AI-generated

Technical impact

A Cross‑Site Request Forgery flaw in the syedamirhussain91 Custom Post custom‑post‑type‑gui plugin allows an attacker to submit a crafted request that stores malicious JavaScript in a custom post. Because the plugin does not verify proper CSRF tokens, a logged‑in administrator or any privileged user can unknowingly save the injected script. Subsequent visitors to the affected post will execute the script in their browsers, potentially exposing session cookies, defacing the site, or facilitating further attacks.

Affected Systems

WordPress installations that use the Custom Post plugin up to and including version 1.0. The flaw is confined to this vendor’s product; no other WordPress core components or plugins are directly implicated.

Risk and Exploitability

The CVSS score of 7.1 places the vulnerability in the high‑severity range. Although the EPSS score is below 1%, indicating low current exploitation probability, the vulnerability is publicly exploitable if the site remains running the affected plugin. The lack of a KEV listing does not diminish the risk; the attack requires only the ability to craft a malicious request, which can be performed from the public internet. Once stored, the XSS runs with the context of any user who views the post, enabling theft of sensitive information or hijacking of user sessions.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Custom Post plugin to the newest release that removes the CSRF flaw.
  • If an update is not immediately available, limit access to the WordPress administration area (e.g., via IP whitelisting or VPN) and ensure that all incoming POST requests to the plugin’s endpoints include a valid CSRF token.
  • Disable or deactivate the Custom Post plugin entirely until the vendor releases a patch and no critical content relies on it.

Generated by OpenCVE AI on May 2, 2026 at 06:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2025-3251 Cross-Site Request Forgery (CSRF) vulnerability in Syed Amir Hussain Custom Post allows Stored XSS.This issue affects Custom Post: from n/a through 1.0.
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L'}

Type Values Removed Values Added
Description Cross-Site Request Forgery (CSRF) vulnerability in Syed Amir Hussain Custom Post allows Stored XSS.This issue affects Custom Post: from n/a through 1.0. Cross-Site Request Forgery (CSRF) vulnerability in syedamirhussain91 Custom Post custom-post-type-gui allows Stored XSS.This issue affects Custom Post: from n/a through <= 1.0.
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Cross-Site Request Forgery (CSRF) vulnerability in Syed Amir Hussain Custom Post allows Stored XSS.This issue affects Custom Post: from n/a through 1.0.
Title WordPress Custom Post plugin <= 1.0 - CSRF to Stored XSS vulnerability
Weaknesses CWE-352
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L'}

Subscriptions

No data.

Weaknesses
  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
Patchstack
Published
Updated
Apr 28, 2026, 4:11 PM
Reserved
Jan 16, 2025, 11:26 AM
Status
Deferred
Published
Jan 16, 2025, 8:15 PM
Modified
Jun 17, 2026, 8:55 AM