Post Voting System Plugin Vulnerability (CVE-2026-89302)

On this page

Security Alert Summary

The Post Voting System WordPress plugin (versions up to and including 1.0) contains an SQL injection vulnerability. The plugin does not properly sanitize and escape a parameter before using it in a SQL query, which allows unauthenticated attackers to perform SQL injection against affected sites.

CVE Details

  • CVE ID: CVE-2026-89302
  • Affected component: Post Voting System WordPress plugin
  • Affected versions: Versions up to and including 1.0 (<= 1.0)
  • Published: October 11, 2026 at 7:17:28 AM UTC
  • Last modified: October 11, 2026 at 12:17:27 PM UTC
  • CVSS v3.1: Base Score 8.6, Severity HIGH, Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
  • Authentication / privileges / user interaction: No authentication required; privileges required: NONE; user interaction: NONE
  • Primary impact: Confidentiality: HIGH; Integrity: NONE; Availability: NONE
  • CWE / weakness: CWE-89 (SQL Injection)

Technical Details

The plugin fails to properly sanitize and escape a parameter before incorporating it into a SQL query. This weakness results in a classic SQL injection vulnerability that can be triggered by unauthenticated users. Because the vulnerability is exploitable over the network without authentication and with low attack complexity, an attacker can craft input that modifies the intended SQL statement.

The provided information does not name specific functions, file paths, or REST endpoints involved; the core issue is the lack of input sanitization and escaping prior to building a database query. The direct impact, as reported, is exposure of confidential data accessible via the affected query. The CVSS vector indicates confidentiality is impacted while integrity and availability are not.

How This Could Impact Your Website

Imagine a typical small site with an owner, an internal editor, and an external contributor who can submit votes or content: an attacker exploiting this SQL injection could retrieve sensitive information from the database that the vulnerable query can access. In practice this might include user records or email addresses stored in the same tables or returned by the affected query. Exposure of internal user email addresses increases the risk of targeted phishing and social engineering against staff, contractors, or frequent contributors.

Even if attackers cannot modify site data or take services offline according to the reported impact, the disclosure of confidential information can harm trust and enable further attacks. professional review may help determine whether your site is affected and how to assess roles and plugins.

Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially contributor-level accounts that accept input.
  • Enforce strong passwords and two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins from your site.
  • Monitor site and database access logs for unusual queries or data access patterns.

If youd like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References