HomeWordPress vulnerabilitiesVK All in One Expansion Unit
VK All in One Expansion Unit vulnerabilities
VK All in One Expansion Unit has 9 known vulnerabilities in this database. The most recent published record is dated 18 Sep 2026.
- Known vulnerabilities
- 9
- Active installs
- 100,000+
- Latest version
- 9.123.1
- Last updated
- 5 Sep 2026
- Most recent
- 18 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-17586 | Medium 6.4 | Up to 9.118.0 | Fixed in a later version (latest 9.123.1) | 18 Sep 2026 |
| Cross-site scripting (XSS) CVE-2025-11737 | Medium 6.4 | Up to 9.112.3 | Fixed in a later version (latest 9.123.1) | 18 Feb 2026 |
| Cross-site scripting (XSS) CVE-2025-11265 | Medium 6.4 | Up to 9.112.1 | Fixed in a later version (latest 9.123.1) | 18 Nov 2025 |
| Cross-site scripting (XSS) CVE-2025-11267 | Medium 6.4 | Up to 9.112.1 | Fixed in a later version (latest 9.123.1) | 18 Nov 2025 |
| Cross-site scripting (XSS) Also reported by JVN Japan CVE-2024-52268 | Medium 4.8 | Not yet published | Check for an update | 13 Nov 2024 |
| Sensitive data exposure CVE-2024-2093 | Medium 6.5 | Before 9.96.0.0 | Fixed in 9.96.0.0 | 9 Apr 2024 |
| Cross-site scripting (XSS) CVE-2024-2170 | Medium 6.4 | Before 9.97.0.0 | Fixed in 9.97.0.0 | 26 Mar 2024 |
| Cross-site scripting (XSS) CVE-2023-0937 | Medium 6.1 | Before 9.87.1.0 | Fixed in 9.87.1.0 | 20 Mar 2023 |
| Cross-site scripting (XSS) CVE-2023-0230 | Medium 5.4 | Before 9.86.0.0 | Fixed in 9.86.0.0 | 27 Feb 2023 |
Read the published descriptions
- CVE-2026-17586, 18 Sep 2026
- The VK All in One Expansion Unit plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'vkExUnit_cta_img_position' Post Meta in all versions up to, and including, 9.118.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The sanitize_text_field callback applied on save does not strip double-quote characters or on* event-handler attributes, and the output filter Vk_Call_To_Action::safe_kses_post() only rewrites disallowed iframe elements while returning all other content verbatim, leaving the injected payload intact in the rendered HTML. CVE record
- CVE-2025-11737, 18 Feb 2026
- The VK All in One Expansion Unit plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'vkExUnit_sns_title' parameter in all versions up to, and including, 9.112.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2025-11265, 18 Nov 2025
- The VK All in One Expansion Unit plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'vkExUnit_cta_url' and 'vkExUnit_cta_button_text' parameters in all versions up to, and including, 9.112.1. This is due to a logic error in the CTA save function that reads sanitization callbacks from the wrong variable ($custom_field_name instead of $custom_field_options), causing the sanitization to never be applied. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that execute when a user accesses an injected page.", CVE record
- CVE-2025-11267, 18 Nov 2025
- The VK All in One Expansion Unit plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '_veu_custom_css' parameter in all versions up to, and including, 9.112.1. This is due to insufficient input sanitization and output escaping on the user-supplied Custom CSS value. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that execute whenever a user accesses an injected page. CVE record
- CVE-2024-52268, 13 Nov 2024
- "Custom Alert Content" of WordPress Plugin "VK All in One Expansion Unit" provided by Vektor,Inc. contains a stored cross-site scripting vulnerability (CWE-79). Umeda Yuugo of Tokyo Denki University reported this vulnerability to IPA. JPCERT/CC coordinated with the developer under Information Security Early Warning Partnership. CVE record
- CVE-2024-2093, 9 Apr 2024
- The VK All in One Expansion Unit plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 9.95.0.1 via social meta tags. This makes it possible for unauthenticated attackers to view limited password protected content. CVE record
- CVE-2024-2170, 26 Mar 2024
- The VK All in One Expansion Unit plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the child page index widget in all versions up to, and including, 9.96.0.1 due to insufficient input sanitization and output escaping on user supplied attributes such as 'className.' This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2023-0937, 20 Mar 2023
- The VK All in One Expansion Unit WordPress plugin before 9.87.1.0 does not escape the $_SERVER['REQUEST_URI'] parameter before outputting it back in an attribute, which could lead to Reflected Cross-Site Scripting in old web browsers CVE record
- CVE-2023-0230, 27 Feb 2023
- The VK All in One Expansion Unit WordPress plugin before 9.86.0.0 does not validate and escape some of its block options before outputting them back in a page/post where the block is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks. CVE record
What to do if you run VK All in One Expansion Unit
If you run VK All in One Expansion Unit, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new VK All in One Expansion Unit vulnerabilities
Free. We email you when a new vulnerability is published for VK All in One Expansion Unit, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.