Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-4300 medium CVSS 6.4

Cross-Site Scripting (XSS) in Robo Gallery (WordPress plugin) (CVE-2026-4300)

Summary

Cross-site scripting in Robo Gallery (WordPress plugin) (CVE-2026-4300). Risk of unauthorized operations or information disclosure. Exploitable via rbs_gallery_LoadingWord.

Original description

The description as published by the source.

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 `` 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.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-4300 has been found in Robo Gallery (WordPress plugin).
Attackers can target a specific entry point like rbs_gallery_LoadingWord over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Robo Gallery (WordPress plugin) CVE-2026-4300" on the vendor's site.

CVE-2026-4300 (Robo Gallery (WordPress plugin)) — CWE-79 / CVSS v3 6.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: rbs_gallery_LoadingWord / rbstext
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in Robo Gallery (WordPress plugin). Attackers reach the vulnerable code path via rbs_gallery_LoadingWord.

📍 Affected scope

Check the vendor advisory for the affected versions of Robo Gallery (WordPress plugin). Attack surface: rbs_gallery_LoadingWord / rbstext.

🔥 Severity

Severity: Medium (CVSS 6.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Robo Gallery (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details