Skip to main content
VulnerabilityPublished

CVE-2026-12800: Premium Packages (WordPress plugin) · SQL Injection

Affects Premium Packages (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 7.5 High.

Data as of 28 Oct 2026, 05:11 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.5% chance of exploitation in 30 days – higher than 75% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jul 2026

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
codename065Premium Packages – Sell Digital Products SecurelyAffected
  • <=6.2.0
Fixed in–

AI-suggested

Until an official fix is released, users should consider disabling or restricting access to the vulnerable REST API endpoint if possible. Monitoring for unusual activity targeting this endpoint is advisable. Avoid using the affected plugin versions in production environments where sensitive data is handled.

Description

The Premium Packages – Sell Digital Products Securely plugin for WordPress is vulnerable to SQL Injection via the 'code' parameter of the POST /wp-json/wpdmpp/v1/cart/coupon REST API endpoint in versions up to, and including, 6.2.0. This is due to insufficient escaping on the user-supplied parameter, which is interpolated directly into a raw SQL query string in the CouponCodes::find() method without use of $wpdb->prepare() or esc_sql(). This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

References

Community reviews

Loading reviews…