CVE-2026-39638
Stored XSS in Qubely Themeum Plugin Affects Versions
Publication date: 2026-04-08
Last updated on: 2026-04-13
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| themeum | qubely | to 1.8.14 (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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how the Cross Site Scripting (XSS) vulnerability in the Qubely plugin directly affects compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
CVE-2026-39638 is a Cross Site Scripting (XSS) vulnerability found in the WordPress Qubely Plugin versions up to and including 1.8.14.
This vulnerability allows an attacker to inject malicious scripts, such as redirects, advertisements, or other HTML payloads, into a website. These scripts execute when visitors access the compromised site.
Exploitation requires a privileged user role, specifically an author or developer, to perform an action like clicking a malicious link, visiting a crafted page, or submitting a form, meaning user interaction is necessary for successful exploitation.
How can this vulnerability impact me? :
If exploited, this vulnerability can lead to the execution of malicious scripts on your website, which may cause unwanted redirects, display of unauthorized advertisements, or other harmful HTML content.
Such actions can degrade user trust, harm your website's reputation, and potentially expose visitors to further attacks.
However, exploitation requires a privileged user role and user interaction, and the vulnerability is considered low priority with moderate risk, making significant impact unlikely.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Qubely plugin once an official patch is released.
Until a patch is available, it is recommended to seek assistance from hosting providers or web developers to help mitigate the risk.
Since exploitation requires a privileged user role (author or developer) and user interaction, limiting such roles and educating users about suspicious links or forms can help reduce risk.