Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Author-level WordPress account
-
DeliveryInject script into gallery setting
-
ExploitStore payload on gallery page
-
ExecutionVictim/admin views gallery frontend
-
PersistScript executes in victim browser
-
ImpactHijack session or escalate privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated account with the Author role or higher on the target WordPress site, because the injection point is a Robo Gallery gallery setting that only such users can edit. The payload only fires when a visitor subsequently loads the frontend page displaying that gallery (the UI:R requirement), so execution depends on victim page views rather than being instant. Limiting factors: the attacker must already hold a semi-trusted content-creator account (not a public/anonymous attacker), the site must run Robo Gallery prior to version 5.2.6, and impact is realized only against users who view the poisoned gallery. |
| Impact | This is a moderate, not top-priority, vulnerability. The signals are mostly consistent: the provided CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:R) describes a network-reachable but privilege- and interaction-gated flaw, which fits a stored XSS requiring an authenticated contributor-class account and a victim who later views the gallery page. A publicly available exploit exists (WPScan), raising the practical likelihood of use, but there is no CISA KEV listing and no EPSS score was supplied, so there is no evidence of active or widespread exploitation - POC availability and active exploitation are distinct signals and should not be conflated. Two internal inconsistencies should be verified: (1) the input rates PR:H, yet the description says the 'Author role and above' is sufficient, and Author is a low-privilege role in WordPress, so PR:L is more defensible - the official rating may overstate the required privilege; (2) the C:H/I:H/A:H impact is unusually high for a reflected-in-DOM stored XSS and appears inflated - typical stored XSS confidentiality/integrity impact is Low with no availability impact. Net: a real but bounded issue requiring a semi-trusted insider account, best treated as standard-priority patching rather than emergency response. |
| Exploit ScenarioDerived | An attacker who has obtained or been granted an Author-level (or higher) account on the WordPress site injects a malicious script into an unsanitised Robo Gallery gallery setting. When any visitor - including a logged-in administrator - views the affected gallery on the frontend, the script executes in their browser, enabling session/cookie theft or actions performed as that higher-privileged user. A public proof-of-concept is available from WPScan, lowering the effort to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
Stored cross-site scripting in the Robo Gallery WordPress plugin before version 5.2.6 allows an authenticated user holding the Author role or higher to save a crafted gallery setting that is later rendered without escaping on the frontend, so the script executes in the browser of any visitor who views the poisoned gallery - including administrators. The injection point is a gallery setting editable only by Author-and-above accounts, and the payload only fires when a victim subsequently loads the affected page, so exploitation requires an authenticated foothold plus victim page views rather than being a one-step anonymous attack. Publicly available exploit code exists (WPScan published the vulnerability entry), but there is no indication of confirmed active exploitation in CISA KEV; the vendor has released a fix in 5.2.6, and this is assessed as a moderate, not top-priority, issue.
RemediationAI
Vendor-released patch: upgrade Robo Gallery to version 5.2.6 or later - this is the only complete fix, since the flaw is in the plugin's own output handling and cannot be corrected from site configuration alone; verify the installed version under Plugins in wp-admin or via WP-CLI (wp plugin list --name=robo-gallery) and confirm the update actually applied, as the affected version range (0 through < 5.2.6) is broad. See the WPScan advisory at https://wpscan.com/vulnerability/e6b574c6-1999-4318-a9aa-9529aeceeb8b/ for the reporter's details. If the upgrade cannot be applied immediately, the highest-value compensating control is to remove the Author-and-above capability to create or edit Robo Gallery galleries - for example by disabling the plugin entirely until patched (trade-off: all existing galleries disappear from the frontend), or by tightening roles so that only fully trusted administrators retain gallery-editing capability (trade-off: breaks contributor workflows and does not protect against a compromised or malicious admin). Because the payload is stored and fires on page view, audit existing galleries for suspicious markup in their settings and re-save or delete any gallery created by an untrusted account, and consider a Content-Security-Policy that disallows inline script on frontend pages (trade-off: may break legitimate theme and plugin inline JavaScript if not staged carefully). Note that WAF rules and output-escaping filters can reduce but not eliminate execution paths, and that public exploit code exists, so exposure should be treated as time-sensitive even though the attack requires an authenticated Author-level account and a victim page view.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation / cross-site scripting) in the WordPress plugin Robo Gallery. The plugin stores gallery configuration values (gallery settings) supplied by a user who can edit the gallery, and later echoes that value into the frontend HTML of a gallery page without sanitising it on input or escaping it on output. Because the tainted value is persisted server-side and re-rendered on every subsequent page load, this is a stored (persistent) XSS rather than a reflected one: the attacker does not need to deliver a crafted link, only to convince a victim to view a page that already contains the poisoned gallery. The affected product identity is captured generically as CPE cpe:2.3:a:unknown:robo_gallery:*:*:*:*:*:*:*:* - the CPE vendor component is recorded as "unknown" and the version component as wildcard, so the CPE should be treated as a coarse product marker rather than an exact version match; the authoritative version constraint comes from the EUVD data (Robo Gallery 0 through < 5.2.6). The technical precondition is WordPress's role/capability model: Author is a semi-trusted content-creator role that can create and manage its own posts but is not an administrator, which is why the exploit chain starts from a low-privilege authenticated account and escalates impact by targeting administrator browsers. Session cookies for WordPress administrators are typically HttpOnly, but stored XSS still enables privileged actions performed through the victim's authenticated browser session, credential-harvesting overlays, rogue admin requests, and site takeover chains. Our independent assessment scores the issue CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N (scope-changed, low confidentiality and integrity impact, no availability impact), which is more conservative than the vendor/NVD-style vector of PR:H/S:U/C:H/I:H/A:H; the higher Base score should be read as treating any authenticated gallery editor as the trigger point and assuming escape from the plugin context into the site's administrative trust boundary.
Know when Robo Gallery gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
Author is a low-privilege role so PR:L not PR:H; stored XSS executing in a victim's browser crosses a scope boundary (S:C) with limited confidentiality/integrity impact and no availability loss.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Robo Gallery WordPress plugin before 5.2.6 does not sanitise and escape a gallery setting before outputting it on a frontend page, allowing users with the Author role and above to perform Stored Cross-Site Scripting attacks that execute in the browser of any visitor viewing a gallery, including administrators.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Robo Gallery
View allStored cross-site scripting in the Robo Gallery WordPress plugin before 5.2.6 lets authenticated users with the Contribu
Stored cross-site scripting in the Robo Gallery WordPress plugin (versions before 5.2.6) lets an authenticated user hold
Stored cross-site scripting in the Robo Gallery WordPress plugin before 5.2.6 lets an authenticated attacker holding the
Auth. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploitable, low attack complexity. Public exploi
The Photo Gallery, Images, Slider in Rbs Image Gallery WordPress plugin before 3.2.24 does not sanitise and escape some
The Photo Gallery, Images, Slider in Rbs Image Gallery WordPress plugin before 3.2.22 does not sanitise and escape some
The Photo Gallery, Images, Slider in Rbs Image Gallery WordPress plugin before 3.2.16 does not sanitise and escape some
A DOM-based Cross-Site Scripting (XSS) vulnerability exists in robosoft Robo Gallery through version 5.1.2, allowing aut
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in robosoft Robo Gall
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in RoboSoft Photo Gal
The Photo Gallery, Images, Slider in Rbs Image Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting
Cross-Site Request Forgery (CSRF) vulnerability in RoboSoft Photo Gallery, Images, Slider in Rbs Image Gallery plugin <=
EUVD-2026-96749
GHSA-fpmp-8c24-ggh8
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB