dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2023-6091

HIGH · 7.2 CVSS v3.1 Published 2024-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Unrestricted Upload of File with Dangerous Type vulnerability in mndpsingh287 Theme Editor.This issue affects Theme Editor: from n/a through 2.7.1.

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 · moderate confidence

The Theme Editor plugin for WordPress by mndpsingh287 versions through 2.7.1 contains an unrestricted file upload vulnerability, allowing attackers to upload dangerous file types (such as executable PHP scripts) without proper validation. This can lead to remote code execution on the affected WordPress site.

MitigationUpdate to the latest version of the Theme Editor if a patch is available; otherwise, disable the plugin until a fix is released. Implement proper file type validation (allowlist approach), restrict upload directories, and disable PHP/executable file execution in upload directories.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Theme Editor plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Theme Editor' by mndpsingh287, or check the /wp-content/plugins/ directory for a theme-editor folder
    Affected if The plugin appears in the list of installed plugins
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Theme Editor and look for the version number displayed below the plugin name, or inspect the main plugin file header for the Version field
    Affected if The version number is 2.7.1 or lower (any version through 2.7.1)
  3. Confirm file upload feature is accessible
    Access the Theme Editor plugin settings page (typically under Appearance > Theme Editor or a dedicated menu item added by the plugin) and locate any file upload or file management functionality
    Affected if The plugin provides a file upload or file creation interface that accepts user-supplied files

A user is affected if the Theme Editor plugin by mndpsingh287 is installed at version 2.7.1 or lower and the file upload feature is active and accessible on their WordPress site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the Theme Editor if a patch is available; otherwise, disable the plugin until a fix is released. Implement proper file type validation (allowlist approach), restrict upload directories, and disable PHP/executable file execution in upload directories.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6091 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6091 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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