CVE-2026-4300
Last modified
CVE-2026-4300 is a medium-severity vulnerability rated 6.4/10 on the CVSS scale. The Robo Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Loading Label' setting in all versions up to, and including, 5.1.3. The plugin uses a custom `|***...***|` marker pattern in its `fixJsFunction()` method to embed raw JavaScript function references within JSON-encoded configuration objects. EPSS estimates a 0.43% chance of exploitation in the next 30 days.
Description
The Robo Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Loading Label' setting in all versions up to, and including, 5.1.3. The plugin uses a custom `|***...***|` marker pattern in its `fixJsFunction()` method to embed raw JavaScript function references within JSON-encoded configuration objects. When a gallery's options are rendered on the frontend, `json_encode()` wraps all string values in double quotes. The `fixJsFunction()` method then strips the `"|***` and `***|"` sequences, effectively converting a JSON string value into raw JavaScript code. The Loading Label field (stored as `rbs_gallery_LoadingWord` post_meta) is an `rbstext` type field that is sanitized with `sanitize_text_field()` on save. While this strips HTML tags, it does not strip the `|***...***|` markers since they contain no HTML. When a user inputs `|***alert(document.domain)***|`, the value passes through sanitization intact, is stored in post_meta, and is later retrieved and output within an inline `<script>` tag via `renderMainBlock()` with the quote markers stripped — resulting in arbitrary JavaScript execution. The gallery post type uses `capability_type => 'post'`, allowing Author-level users to create galleries. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses a page containing the gallery shortcode.
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-4300?
How severe is CVE-2026-4300?
How do I fix CVE-2026-4300?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-42993Heap-based buffer overflow in Remote Desktop Client allows a…7.5
- CVE-2026-42994Bitwarden CLI 2026.4.0 from 2026-04-22T21:57Z to 2026-04-22T…9.8
- CVE-2026-42996JS8Call through 2.3.1 and JS8Call-improved before 3.0 have a…10
- CVE-2026-42997An issue was discovered in idrac in OpenStack Ironic before …7.7
- CVE-2026-42998An issue was discovered in OpenStack Keystone before 29.0.2.…8.8
- CVE-2026-42999An issue was discovered in OpenStack Keystone before 29.0.2.…8.8
- CVE-2026-43000An issue was discovered in OpenStack Keystone before 29.0.2.…8.8
- CVE-2026-43001An issue was discovered in OpenStack Keystone before 29.0.2.…8
- CVE-2026-43002An issue was discovered in OpenStack Horizon 25.6 and 25.7 b…5.3
- CVE-2026-43003An issue was discovered in OpenStack ironic-python-agent 1.0…7.5
- CVE-2026-43004In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-43005In the Linux kernel, the following vulnerability has been re…7.1
Are you affected by CVE-2026-4300?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
