CVE-2026-82227: WordPress WPBulky plugin <= 1.2.2 - SQL Injection vulnerability

Published Aug 28, 2026
·
Updated

Contributor SQL Injection in WPBulky <= 1.2.2 versions.

Affected Software

1 affected component
WordPress WPBulky plugin<=1.2.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade WordPress WPBulky plugin to a version that resolves this vulnerability.

    Fixed in 1.2.3

Event History

Aug 28, 2026
CVE Published
via MITRE·02:33 PM
Data Sourced
via MITRE·02:33 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

Does exploitation require an authenticated WordPress account?

Yes. The vulnerability is rated PR:L and is described as a contributor SQL injection issue, indicating that an attacker needs low-privileged access such as a Contributor account.

2

Is a site exposed to unauthenticated internet attackers?

The provided CVSS vector does not indicate unauthenticated exploitation: it requires low privileges. Sites that allow untrusted users to hold Contributor-level accounts are the most directly exposed.

3

What is the expected impact if the vulnerability is exploited?

The CVSS metrics indicate high confidentiality impact and low availability impact, with no integrity impact listed. The scope is marked changed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203