LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6091: WordPress Theme Editor plugin <= 2.7.1 - Arbitrary File Upload vulnerability

Unrestricted Upload of File with Dangerous Type vulnerability in mndpsingh287 Theme Editor.This issue affects Theme Editor: from n/a through 2.7.1.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE affects the WordPress Theme Editor plugin through 2.7.1. A highly privileged authenticated user could upload a dangerous file type. If abused, this can compromise site confidentiality, integrity, and availability. The source bundle does not show active exploitation or a confirmed fixed version.

Executive priority

Treat as high priority for WordPress environments using this plugin, especially public sites or sites with many administrators. The privilege requirement reduces likelihood, but impact can be severe if an admin account is compromised.

Technical view

CVE-2023-6091 is a CWE-434 unrestricted file upload issue in mndpsingh287 Theme Editor for WordPress, affecting versions through 2.7.1. CVSS 3.1 is 7.2 high, with network access, low complexity, high privileges required, no user interaction, unchanged scope, and high CIA impact.

Likely exposure

Exposure is limited to WordPress sites running the Theme Editor plugin version 2.7.1 or earlier. Risk is highest where many users hold high-privilege WordPress roles or admin accounts are weakly protected.

Exploitation context

The source bundle does not identify active exploitation, and KEV is false. The CVSS vector indicates exploitation requires high privileges but no user interaction. Successful abuse could allow upload of dangerous file types, creating a serious site compromise path.

Researcher notes

Evidence is limited to CVE metadata and the Patchstack database reference in the bundle. No exploit status, fixed version, or vendor remediation details are provided here, so avoid assuming patch availability without checking current vendor guidance.

Mitigation direction

  • Inventory WordPress sites for the Theme Editor plugin and version.
  • Remove or disable the plugin where it is not operationally required.
  • Check vendor, WordPress, and Patchstack guidance for a fixed release.
  • Restrict high-privilege WordPress accounts and enforce MFA where available.
  • Review file upload permissions and web-accessible upload locations.

Validation and detection

  • Confirm whether Theme Editor is installed and at version 2.7.1 or earlier.
  • List users with administrator or equivalent high-privilege WordPress roles.
  • Review recent plugin-related file changes for unexpected uploaded files.
  • Check web server logs for unusual authenticated upload activity.
  • Verify any applied update or removal across all WordPress instances.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-6091 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2023-6091Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
mndpsingh287Theme Editortheme-editor, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.