Quick answers
- Is CVE-2026-82227 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82227 being exploited in the wild.
- How severe is CVE-2026-82227?
- High severity, with a CVSS score of 8.5, published 28 August 2026.
- Which products and versions are affected?
- VillaTheme WPBulky 1.2.2 and earlier.
- Is there a fix for CVE-2026-82227?
- A patch was published on 2026-08-28: Version 1.2.3 available as patch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82227 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82227?
- Check whether you run VillaTheme WPBulky at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a SQL injection flaw (CWE-89) in WPBulky versions 1.2.2 and earlier, requiring contributor-level privileges to exploit. The root cause appears to be insufficient input sanitization in the bulk editing functionality. An authenticated attacker with contributor role can craft malicious SQL queries through the plugin's interface to read, modify, or delete database records. The attack vector is network-based but requires valid WordPress contributor credentials. A patch was released in version 1.2.3.
Affected products
- VillaTheme WPBulky 1.2.2 and earlier
Timeline
- 2026-08-25: disclosed: Reported by JunHee CHO
- 2026-08-28: advisory: Published by Patchstack
- 2026-08-28: patched: Version 1.2.3 available as patch