EUVD-2026-20435
GHSA-f324-cf3c-hqgv
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Stored cross-site scripting in Robo Gallery for WordPress up to version 5.1.3 allows authenticated Author-level users to inject arbitrary JavaScript via the Loading Label gallery setting. The vulnerability exploits a custom marker pattern (|*...*|) in the fixJsFunction() method that converts JSON-wrapped strings into raw JavaScript code; input validation with sanitize_text_field() fails to strip the markers, enabling script injection that executes whenever the gallery shortcode is rendered. No public exploit code or active exploitation has been confirmed at time of analysis.
Technical ContextAI
The Robo Gallery plugin uses a non-standard approach to embed JavaScript function references within JSON configuration objects. The fixJsFunction() method in jsoptions.php processes gallery options by searching for the |*...*| marker pattern and stripping the surrounding quote and marker characters, converting what PHP's json_encode() wrapped as a string value into executable JavaScript. The Loading Label field (rbs_gallery_LoadingWord post_meta) is an rbstext field type sanitized via WordPress's sanitize_text_field() function on save. While this removes HTML tags, it does not filter the pipe, asterisk, or other characters in the |*...*| pattern since they are not HTML. When the gallery renders via renderMainBlock() in layout.v1.php and grid.v1.php, configuration data is embedded in an inline <script> tag with the markers stripped-causing any payload within the markers to execute as JavaScript. The root cause is improper output encoding combined with a secondary input validation bypass; the markers were intended as a safe abstraction but lack adequate sanitization. This falls under CWE-79 (Cross-site Scripting) because user-controlled input reaches the browser without proper escaping.
RemediationAI
Upgrade Robo Gallery to a patched version released after 5.1.3 when available. In the interim, disable gallery creation permissions for untrusted Author-level users, restricting creation to Editors or Administrators only, or deactivate the plugin if not actively used. Site administrators should review all existing galleries for suspicious Loading Label values containing unusual markers or JavaScript keywords (alert, eval, fetch, XMLHttpRequest, etc.) via the post_meta table or gallery edit interface. The plugin developer should update sanitize_text_field() to explicitly strip the |* and *| markers before storage, or redesign the configuration encoding to use a safer abstraction (e.g., boolean flags or enum values instead of marker-based string transformation). Refer to the Wordfence threat intelligence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/d8693b7d-693f-450a-89ef-e936a8813ca9?source=cve for additional context and monitoring recommendations.
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Country State City Dropdown CF7 plugin for WordPress is vulnerable to SQL Injection via the ‘cnt’ and 'sid' paramete
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today