Description
The GutenKit WordPress plugin before 2.5.5 does not properly sanitize custom CSS saved against a post before printing it inside an inline style block on the published page, allowing users with the Author role and above to break out of the style element and store JavaScript that executes in the browser of any visitor who views the post. Exploitation affects sites running WordPress below 7.0.
Published: 2026-11-06
Score: n/a
EPSS: n/a
KEV: No
Impact: Stored Cross‑Site Scripting
Action: Patch ASAP
AI Analysis

Impact

The GutenKit WordPress plugin, prior to version 2.5.5, fails to sanitize custom CSS entered in page settings. A user with the Author role or higher can embed JavaScript that escapes the style element and is stored in the post. When a visitor loads the published page, the malicious script executes in the visitor’s browser, enabling full client‑side compromise, including session hijacking, cookie theft, or redirection to phishing sites. The flaw represents a classic stored cross‑site scripting weakness.

Affected Systems

Any WordPress site using the GutenKit plugin in its 2.5.0 through 2.5.4 releases, running WordPress versions below 7.0, is affected. The plugin vendor is listed as Unknown:GutenKit, indicating an unregistered or third‑party developer.

Risk and Exploitability

There is no CVSS score or EPSS data available, but the vulnerability is exploitable by any author‑level user on the site without external access, making it trivial to launch the attack. Because the malicious code runs in every visitor’s browser, the impact is potentially global. The vulnerability is not included in CISA’s KEV catalogue, yet the ease of exploitation and wide impact warrant rapid remediation.

Generated by OpenCVE AI on November 6, 2026 at 07:27 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the newest GutenKit release (2.5.5 or later) which incorporates proper input sanitization for custom CSS.
  • If upgrading is not immediately possible, restrict the ability of Authors and lower roles to edit page custom CSS or disable the custom CSS feature entirely.
  • Scan the database for posts containing custom CSS, remove or sanitize any injected scripts, and verify that the remaining CSS is clean.
  • Consider limiting the use of custom CSS in page settings or moving such functionality to a trusted custom‑plugin that enforces strict validation.

Generated by OpenCVE AI on November 6, 2026 at 07:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 06 Nov 2026 07:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-79
CWE-93

Fri, 06 Nov 2026 06:15:00 +0000

Type Values Removed Values Added
Description The GutenKit WordPress plugin before 2.5.5 does not properly sanitize custom CSS saved against a post before printing it inside an inline style block on the published page, allowing users with the Author role and above to break out of the style element and store JavaScript that executes in the browser of any visitor who views the post. Exploitation affects sites running WordPress below 7.0.
Title GutenKit 2.5.0 - 2.5.4 - Author+ Stored XSS via Page Settings Custom CSS
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-11-06T06:00:25.090Z

Reserved: 2026-10-21T13:29:11.377Z

Link: CVE-2026-114427

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-06T06:16:40.160

Modified: 2026-11-06T06:16:40.160

Link: CVE-2026-114427

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-06T07:30:09Z

Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

  • CWE-93

    Improper Neutralization of CRLF Sequences ('CRLF Injection')