Plugins · vk-blocks · data as of 2026-11-04
Is VK Blocks safe? Known vulnerabilities and latest version
- Latest version
- 1.130.0
- Last updated
- 2026-11-02
- Active installs
- 100,000+
- Known issues on record
- 5
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
This is a plugin that extends Gutenberg's blocks. — by Vektor,Inc.
What to do
- Update to the latest version (1.130.0). Anything older than 1.126.2 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get vk-blocks --field=version shows what you run; wp plugin update vk-blocks updates it.
Check your version
Known vulnerabilities
5 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 6.4 CVE-2026-78087 · published 2026-10-15
Stored cross-site scripting (XSS) in VK Blocks (1.126.1 and older)
- Affected
- 1.126.1 and older
- Fixed in
- 1.126.2 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The VK Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Group Block 'linkToPost' Feature in all versions up to, and including, 1.126.1 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.
medium 4.3 CVE-2024-13635 · published 2025-03-07
Information disclosure in VK Blocks (1.94.2.2 and older)
- Affected
- 1.94.2.2 and older
- Fixed in
- 1.95.0.3 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The VK Blocks plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.94.2.2 via the page content block. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive data including the content of private posts and pages.
NVD CVE-2024-13635Wordfence advisoryCode change (fix)Plugin source
medium 5.4 CVE-2023-5706 · published 2023-11-22
Stored cross-site scripting (XSS) in VK Blocks (1.63.0.1 and older)
- Affected
- 1.63.0.1 and older
- Fixed in
- 1.64.0.0 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The VK Blocks plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'vk-blocks/ancestor-page-list' block in all versions up to, and including, 1.63.0.1 due to insufficient input sanitization and output escaping on user supplied attributes. 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.
NVD CVE-2023-5706Wordfence advisoryCode change (fix)Plugin source
medium 4.3 CVE-2023-0583 · published 2023-06-03
Missing authorization check in VK Blocks (1.57.0.5 and older)
- Affected
- 1.57.0.5 and older
- Fixed in
- 1.57.1.0 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The VK Blocks plugin for WordPress is vulnerable to improper authorization via the REST 'update_vk_blocks_options' function in versions up to, and including, 1.57.0.5. This allows authenticated attackers, with contributor-level permissions or above, to change plugin settings including default icons.
NVD CVE-2023-0583Wordfence advisoryCode change (fix)Plugin source
medium 4.3 CVE-2023-0584 · published 2023-06-03
Missing authorization check in VK Blocks (1.57.0.5 and older)
- Affected
- 1.57.0.5 and older
- Fixed in
- 1.57.1.0 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The VK Blocks plugin for WordPress is vulnerable to improper authorization via the REST 'update_options' function in versions up to, and including, 1.57.0.5. This allows authenticated attackers, with contributor-level permissions or above, to change the 'vk_font_awesome_version' option to an arbitrary value.
NVD CVE-2023-0584Wordfence advisoryCode change (fix)Plugin source
Recent activity
- 2026-11-02 — latest release on wordpress.org (1.130.0).
- 2026-10-15 — Stored cross-site scripting (XSS) disclosed (CVE-2026-78087), fixed in 1.126.2.
- 2025-03-07 — Information disclosure disclosed (CVE-2024-13635), fixed in 1.95.0.3.
- 2023-11-22 — Stored cross-site scripting (XSS) disclosed (CVE-2023-5706), fixed in 1.64.0.0.
Get an email when VK Blocks has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for VK Blocks (vk-blocks) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by Vektor,Inc. (2 tracked)
Types found in this plugin: Cross-site scripting (XSS) (2) · Missing authorization (2) · Sensitive data exposure (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/vk-blocks (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/vk-blocks"><img src="https://laskyr.com/plugins/vk-blocks/badge.svg" alt="VK Blocks vulnerability status"></a>