CVE-2025-6784
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 Code Engine plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 0.3.5 via the 'code-engine' shortcode. This is due to the plugin not restricting access to the code injecting functionality of the plugin. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server.
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 Code Engine WordPress plugin (versions up to 0.3.5) contains an authenticated Remote Code Execution vulnerability via the 'code-engine' shortcode. The plugin fails to implement proper capability checks, allowing any authenticated user with Contributor-level access or higher to inject and execute arbitrary server-side code through the shortcode functionality.
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.
-
Verify Code Engine plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Code Engine' or check the plugin files in wp-content/plugins/code-engine/ for a version fileAffected if The Code Engine plugin is present on the WordPress site
-
Check installed plugin versionIn Plugins list view, look at the version column for Code Engine, or open the main plugin PHP file and look for 'Version:' in the plugin header commentAffected if Version is 0.3.5 or lower, or the version cannot be determined (indicating an old unmaintained copy)
-
Confirm shortcode is accessible to low-privilege usersAttempt to use the shortcode [code-engine] with a test Contributor-level user account, or inspect the plugin PHP code for capability checks before the code execution logicAffected if The shortcode executes code without checking if the user has administrator privileges or a specific capability like 'manage_options'
-
Identify users with Contributor-level accessIn WordPress admin, go to Users > All Users and review the role column for accounts assigned 'Contributor' role or higher (Author, Editor, Administrator)Affected if There are user accounts with Contributor, Author, Editor, or Administrator roles who can access the shortcode functionality
A site is affected if Code Engine plugin version 0.3.5 or lower is installed AND the shortcode is accessible to authenticated users with Contributor-level permissions or higher.
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 dataUpdate the Code Engine plugin to version 0.3.6 or later once available. In the interim, restrict or disable the 'code-engine' shortcode via plugin settings or remove/disable the plugin entirely if no patch is imminent.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6784 — 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-2025-6784 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