Plugins · premmerce-dev-tools · data as of 2026-11-04
Is Premmerce Dev Tools safe? Known vulnerabilities and latest version
- Status
- Closed 2026-06-10
- Known issues on record
- 1
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate premmerce-dev-tools && wp plugin delete premmerce-dev-tools
Check your version
Known vulnerabilities
1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 1 record(s) do not state which versions are affected.
high 8.8 CVE-2026-6933 · published 2026-06-16
Remote code execution in Premmerce Dev Tools (2.0 and older)
- Affected
- 2.0 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Premmerce Dev Tools plugin for WordPress is vulnerable to Remote Code Execution via missing authorization in versions up to and including 2.0. This is due to the 'generatePluginHandler' function lacking any authorization check before processing user-supplied POST data, combined with the 'createFromStub' function performing unsanitized string substitution of the 'premmerce_plugin_namespace' parameter directly into PHP stub files written to the wp-content/plugins/ directory. An attacker can inject a semicolon followed by arbitrary PHP code into the namespace parameter, causing the generated plugin file to contain and execute that code when accessed via HTTP. This makes it possible for authenticated attackers with Subscriber-level access and above to create arbitrary PHP files on the server and achieve remote code execution.
Recent activity
- 2026-06-10 — closed on wordpress.org (Security Issue).
- 2026-06-16 — Remote code execution disclosed (CVE-2026-6933), fix version not stated.
Get an email when Premmerce Dev Tools has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Premmerce Dev Tools (premmerce-dev-tools) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Remote code execution (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/premmerce-dev-tools (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/premmerce-dev-tools"><img src="https://laskyr.com/plugins/premmerce-dev-tools/badge.svg" alt="Premmerce Dev Tools vulnerability status"></a>