The Productive Commerce WordPress plugin before 1.1.54 does not sanitise and escape a parameter before using it in a
Source GCVE Database
Not known to be exploited : upgrade to 1.1.54 soon.
Data as of 8 Nov 2026, 08:05 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 1.1.54
Exploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 7 Nov 2026.
What to do
Upgrade Productive Commerce (WordPress plugin) to 1.1.54.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Productive Commerce | Affected
| Fixed in
|
AI-suggested
Upgrade the Productive Commerce WordPress plugin to version 1.1.54 or later where this vulnerability is fixed. No other mitigation guidance is provided, and no indication exists that the vulnerability is already mitigated or requires no action.
Description
The Productive Commerce WordPress plugin versions before 1.1.54 contain a vulnerability where a parameter is not properly sanitized and escaped before being used in a SQL statement. This flaw allows unauthenticated attackers to perform SQL injection attacks against affected installations.