UiChemy stored XSS via 'head' parameter
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The UiChemy WordPress plugin has a stored cross-site scripting flaw in its 'head' parameter that lets an attacker with editor-level access or higher inject scripts into pages. The attacker reaches it over the network, and the scripts run whenever a user opens an injected page.
Written by a model
Original description
The UiChemy – Convert Figma, Prompts and AI Builds to Elementor, Gutenberg and Bricks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'head' parameter in all versions up to, and including, 5.6.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. On a default single-site WordPress installation, Editors hold the 'unfiltered_html' capability, meaning the plugin's only effective gate passes for Editor-level users, and the secondary UiChemy_Roles check is a no-op on the Free build and default Pro configuration.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131580 (UiChemy <= 5.6.1 - Authenticated (Editor+) Stored Cross-Site Scripting via 'head' Parameter), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131580 (entry last updated 2026-11-20):
Affected:
- posimyththemes UiChemy – Convert Figma, Prompts and AI Builds to Elementor, Gutenberg and Bricks: through 5.6.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131580 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131580 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/9b44c5e9-1330-4e8f-a992-789d072697a8?source=cve
- https://plugins.trac.wordpress.org/browser/uichemy/tags/5.6.1/uichemy-composer/includes/admin/class-uichemy-composer-manager.php#L7978
- https://plugins.trac.wordpress.org/browser/uichemy/tags/5.6.1/uichemy-composer/includes/admin/class-uichemy-composer-manager.php#L7796
- https://plugins.trac.wordpress.org/browser/uichemy/tags/5.6.1/uichemy-composer/includes/admin/class-uichemy-composer-manager.php#L3872
- https://plugins.trac.wordpress.org/browser/uichemy/tags/5.6.1/uichemy-composer/includes/admin/class-uichemy-composer-manager.php#L230
- https://plugins.trac.wordpress.org/changeset?old_path=/uichemy/tags/5.6.1&new_path=/uichemy/tags/5.7.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131580
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131580"}.Affected versions
- posimyththemes UiChemy – Convert Figma, Prompts and AI Builds to Elementor, Gutenberg and Bricksthrough 5.6.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.4/10CVSS 4.4
- No patch5/5No patch listed yet
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 7
Questions about CVE-2026-131580
Is CVE-2026-131580 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-131580?
UiChemy – Convert Figma, Prompts and AI Builds to Elementor, Gutenberg and Bricks: through 5.6.1.
Source: cve.now feed data
Related
- CVE-2026-133419UiChemy <= 5.5.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'sections[0][settings][raw_css]' Parameter
- CVE-2026-109385UiChemy <= 5.3.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Slot Link URL
- CVE-2026-125085Nexter Extension <= 4.9.0 - Authenticated (Subscriber+) Privilege Escalation to 'reset-view' Parameter
- CVE-2026-0726Nexter Extension – Site Enhancements Toolkit <= 4.4.6 - Unauthenticated PHP Object Injection via 'nxt_unserialize_replace'
- CVE-2026-111114Nexter Extension <= 4.7.11 - Authenticated (Subscriber+) Privilege Escalation to 'reset-view' Parameter
- CVE-2026-15285The Plus Addons for Elementor <= 6.4.11 - Authenticated (Contributor+) Stored Cross-Site Scripting via Button Widget Custom Attributes
No corrections so far. Something wrong on this page? Report an error.