Quick answers
- Is CVE-2026-89237 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-89237 being exploited in the wild.
- How severe is CVE-2026-89237?
- Informational severity, published 26 September 2026.
- Which products and versions are affected?
- WPScan Bluff Post through 1.1.1.
- Is there a fix for CVE-2026-89237?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-89237 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-89237?
- Check whether you run WPScan Bluff Post 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 plugin does not sanitize or escape the 'table_name' and 'column_name' parameters before using them as identifiers in SQL queries, enabling SQL injection (CWE-89). This unauthenticated attack vector allows attackers to append arbitrary SQL commands to extract sensitive information from the database. No patch is currently known to be available.
Affected products
- WPScan Bluff Post through 1.1.1
Timeline
- 2026-09-23: disclosed
- 2026-09-26: advisory