Technical impact
The All‑in‑One Video Gallery plugin for WordPress is vulnerable to stored cross‑site scripting because the custom field "embedcode" is accepted without sanitization and later output without proper escaping. The vulnerability is triggered when the save_meta_data() handler returns early because the $_POST['post_type'] field is absent, a condition that always occurs during XML‑RPC requests. Subscribers and higher roles receive the publish_aiovg_videos capability, allowing any authenticated user with at least subscriber access to submit a malicious embedcode via a single wp.newPost XML‑RPC call, causing arbitrary JavaScript to run for any user who views the infected page. The flaw resides entirely in the core handling of custom fields and is independent of the video hosting provider. Whether a site hosts videos locally, on YouTube, or on Vimeo, the same code processes the embedcode field. The problem is limited to the stored severity of XSS; it does not directly affect file upload, authentication, or privilege escalation mechanisms. The impact is that malicious scripts executed in the site context can be used for attacks such as session hijacking or data theft, but those consequences are not expressly documented in the official description.
Affected Systems
Any WordPress site that has the All‑in‑One Video Gallery plugin installed in a version up to and including 4.9.7. The vulnerability applies to all editions of the plugin, regardless of whether videos are hosted locally, on YouTube, or on Vimeo, because the issue originates in the plugin’s handling of the embedcode custom field rather than in any particular hosting configuration.
Risk and Exploitability
The CVSS score of 6.4 indicates moderate severity. EPSS data is not available, and the vulnerability is not listed in the CISA KEV catalog. The attack requires only authenticated access with subscriber privileges and a single XML‑RPC wp.newPost call. Because XML‑RPC is often enabled by default on WordPress installations and the plugin grants Subscribers the publishing capability, exploitation is straightforward for any user who can log in. The risk to affected sites is therefore moderate to significant, especially for those that maintain XML‑RPC enabled and give publishing rights to subscribers.