Is WPBulky safe to use?

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

Which versions of WPBulky are vulnerable?

Known issues on record (newest first): SQL injection (1.2.2 and older, fixed in 1.2.3); SQL injection (1.1.13 and older, fixed in 1.1.14); Stored cross-site scripting (XSS) (older than 1.0.10, fixed in 1.0.10). The full list with sources is on this page.

What is the latest version of WPBulky?

1.2.3, according to wordpress.org (last updated 2026-08-27). It has 400+ active installs.

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

Take a backup, then update it from Dashboard > Updates (or run wp plugin update wpbulky-wp-bulk-edit-post-types). 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 · wpbulky-wp-bulk-edit-post-types · data as of 2026-11-04

Is WPBulky safe? Known vulnerabilities and latest version

Latest version: 1.2.3
Last updated: 2026-08-27
Active installs: 400+
Known issues on record: 3
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 7.4+

A helpful tool that allows you to bulk edit post types (posts, pages, media, comments...) — by VillaTheme

What to do

Update to the latest version (1.2.3). Anything older than 1.2.3 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 wpbulky-wp-bulk-edit-post-types --field=version shows what you run; wp plugin update wpbulky-wp-bulk-edit-post-types updates it.

Check your version

Known vulnerabilities

3 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.

high 8.5 CVE-2026-82227 · published 2026-08-28

SQL injection in WPBulky (1.2.2 and older)

Affected: 1.2.2 and older
Fixed in: 1.2.3
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Contributor SQL Injection in WPBulky <= 1.2.2 versions.

NVD CVE-2026-82227 Patchstack advisory

high 7.6 CVE-2025-68550 · published 2025-12-23

SQL injection in WPBulky (1.1.13 and older)

Affected: 1.1.13 and older
Fixed in: 1.1.14
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in VillaTheme WPBulky wpbulky-wp-bulk-edit-post-types allows Blind SQL Injection.This issue affects WPBulky: from n/a through <= 1.1.13.

NVD CVE-2025-68550 Patchstack advisory

medium 5.4 CVE-2023-30482 · published 2023-08-08

Stored cross-site scripting (XSS) in WPBulky (older than 1.0.10)

Affected: older than 1.0.10
Fixed in: 1.0.10
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

Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in VillaTheme WPBulky plugin <= 1.0.10 versions.

NVD CVE-2023-30482 Patchstack advisory

Recent activity

2026-08-27 — latest release on wordpress.org (1.2.3).
2026-08-28 — SQL injection disclosed (CVE-2026-82227), fixed in 1.2.3.
2025-12-23 — SQL injection disclosed (CVE-2025-68550), fixed in 1.1.14.
2023-08-08 — Stored cross-site scripting (XSS) disclosed (CVE-2023-30482), fixed in 1.0.10.

Free. We check the CVE feeds every day and email you only when a new issue for WPBulky (wpbulky-wp-bulk-edit-post-types) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: SQL injection (2) · Cross-site scripting (XSS) (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/wpbulky-wp-bulk-edit-post-types (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/wpbulky-wp-bulk-edit-post-types"><img src="https://laskyr.com/plugins/wpbulky-wp-bulk-edit-post-types/badge.svg" alt="WPBulky vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is WPBulky safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (1.2.3)

What to do

Check your version

Known vulnerabilities

SQL injection in WPBulky (1.2.2 and older)

SQL injection in WPBulky (1.1.13 and older)

Stored cross-site scripting (XSS) in WPBulky (older than 1.0.10)

Recent activity

Get an email when WPBulky has a new vulnerability

Browse vulnerabilities

Where this data comes from