CVE-2026-1097
Stored XSS in ThemeRuby Multi Authors WordPress Plugin
Publication date: 2026-01-24
Last updated on: 2026-04-08
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| themeruby | multi_authors | to 1.0.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the ThemeRuby Multi Authors WordPress plugin. It occurs because the plugin does not properly sanitize and escape input for the 'before' and 'after' shortcode attributes. Authenticated users with Contributor-level access or higher can inject malicious scripts into pages via these attributes. When other users view the affected pages, the injected scripts execute in their browsers, potentially compromising their security.
How can this vulnerability impact me? :
The vulnerability allows authenticated users with Contributor-level access or above to inject arbitrary web scripts into pages. This can lead to malicious scripts executing in the browsers of users who view those pages, potentially resulting in theft of user data, session hijacking, defacement, or other malicious actions that compromise the integrity and security of the website and its users.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should update the ThemeRuby Multi Authors – Assign Multiple Writers to Posts plugin to a version later than 1.0.0 where the input sanitization and output escaping issues with the 'before' and 'after' shortcode attributes are fixed. Additionally, restrict Contributor-level access and above to trusted users only, as the vulnerability requires authenticated users with at least Contributor privileges to exploit. Monitoring and disabling the affected shortcodes or removing the plugin until a patch is applied can also reduce risk.