CVE-2026-6933
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Premmerce Dev Tools WordPress plugin (versions up to 2.0) has an authenticated RCE vulnerability where the generatePluginHandler function lacks authorization checks and the createFromStub function performs unsanitized string substitution of the premmerce_plugin_namespace POST parameter into PHP stub files in wp-content/plugins/. Attackers with Subscriber-level access can inject a semicolon followed by arbitrary PHP code into the namespace parameter to create and execute malicious PHP files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Premmerce Dev Tools plugin is installedInspect the wp-content/plugins/ directory for a folder named premmerce-dev-tools or check the WordPress admin Plugins pageAffected if The plugin directory exists in wp-content/plugins/
-
Determine the installed plugin versionOpen the main plugin file (usually premmerce-dev-tools.php or index.php) and locate the Version header in the plugin comment block, or check via WordPress admin Plugins listAffected if The version is 2.0 or lower (versions up to 2.0 are affected)
-
Verify if Subscriber-level user accounts existQuery the wp_users and wp_usermeta tables or check the WordPress admin Users panel for any user with the Subscriber roleAffected if At least one user with Subscriber role exists (attackers need Subscriber-level access)
-
Inspect wp-content/plugins/ for unexpected PHP filesList all PHP files in wp-content/plugins/ and check for files with suspicious names, recent modification dates, or code containing eval(), base64_decode(), shell_exec(), or similar dangerous functionsAffected if Unexpected or malicious PHP files are present in the plugins directory
-
Review access logs for plugin endpoint abuseSearch server access logs for POST requests to /wp-admin/admin-ajax.php or direct plugin files containing the string 'generatePluginHandler' or 'premmerce_plugin_namespace'Affected if Suspicious POST requests to the plugin's handler functions are found
A user is affected if the Premmerce Dev Tools plugin (version 2.0 or lower) is installed and at least one Subscriber-level user account exists in the WordPress environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately disable or remove the Premmerce Dev Tools plugin if not needed, or update to a patched version if available. Audit wp-content/plugins/ for unexpected PHP files and remove any malicious code discovered.
- Consultation3.0 h
- Implementation5.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6933 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6933 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data