Is Blockons safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (1.2.20). As of 2026-11-04. 2 issues are on record for older versions; version 1.2.20 or newer fixes all of them that state a fix. Keep Blockons on the latest version (1.2.20) and remove it if you do not use it.

Which versions of Blockons are vulnerable?

Known issues on record (newest first): Stored cross-site scripting (XSS) (1.2.19 and older, fixed in 1.2.20); Missing authorization check (1.2.19 and older, fixed in 1.2.20). The full list with sources is on this page.

What is the latest version of Blockons?

1.2.20, according to wordpress.org (last updated 2026-10-15). It has 700+ active installs.

What should I do if my Blockons is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update blockons). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · blockons · data as of 2026-11-04

Is Blockons safe? Known vulnerabilities and latest version

Latest version: 1.2.20
Last updated: 2026-10-15
Active installs: 700+
Known issues on record: 2
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 5.6+

Enhanced WordPress editor blocks for Gutenberg, including core Block Extensions and Site Addons for your WordPress site and WooCommerce online store — by Kaira

What to do

Update to the latest version (1.2.20). Anything older than 1.2.20 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 blockons --field=version shows what you run; wp plugin update blockons updates it.

Check your version

Known vulnerabilities

2 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.5 CVE-2026-24550 · published 2026-01-23

Stored cross-site scripting (XSS) in Blockons (1.2.19 and older)

Affected: 1.2.19 and older
Fixed in: 1.2.20 *
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 Patchstack

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Kaira Blockons blockons allows Stored XSS.This issue affects Blockons: from n/a through <= 1.2.19.

NVD CVE-2026-24550 Patchstack advisory

high 7.5 CVE-2025-14360 · published 2026-01-08

Missing authorization check in Blockons (1.2.19 and older)

Affected: 1.2.19 and older
Fixed in: 1.2.20 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in Kaira Blockons blockons allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Blockons: from n/a through <= 1.2.19.

NVD CVE-2025-14360 Patchstack advisory

Recent activity

2026-10-15 — latest release on wordpress.org (1.2.20).
2026-01-23 — Stored cross-site scripting (XSS) disclosed (CVE-2026-24550), fixed in 1.2.20.
2026-01-08 — Missing authorization check disclosed (CVE-2025-14360), fixed in 1.2.20.

Free. We check the CVE feeds every day and email you only when a new issue for Blockons (blockons) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (1) · Missing authorization (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/blockons (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/blockons"><img src="https://laskyr.com/plugins/blockons/badge.svg" alt="Blockons vulnerability status"></a>

← Check another plugin · Free hacked-site scan