CVE-2026-109926 Productive Commerce < 1.1.49 - Subscriber+ Arbitrary Plugin Activation
Medium 4.3
Published
Updated
Check this codebase for CVE-2026-109926 and fix it if it is affected.
What it is: CVE-2026-109926 is a medium-severity vulnerability in Unknown Productive Commerce, published on 21 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-109926 in the wild and no public exploit code.
Affected product: Unknown Productive Commerce. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-109926/ (Markdown: https://insights.sbomify.com/CVE-2026-109926/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-109926?
CVE-2026-109926 is a medium-severity vulnerability in Unknown Productive Commerce, published on 21 Oct 2026.
Official description
The Productive Commerce WordPress plugin before 1.1.49 does not perform a capability check in one of its AJAX actions and exposes the nonce that guards it on every admin-area page, allowing any authenticated user such as a subscriber to activate arbitrary Productive Commerce WordPress plugin before 1.1.49 already installed on the site.
Weakness: CWE-862
Which versions are affected by CVE-2026-109926?
How do I fix CVE-2026-109926?
No fix has been published for CVE-2026-109926 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-109926 being exploited?
There is no known exploitation of CVE-2026-109926 in the wild and no public exploit code.
Sources
Also known as GHSA-h4jv-2hjr-9f5x.