LiveActive security incident?Get immediate response
CVE Record

CVE-2022-34154: WordPress Enable SVG, WebP & ICO Upload plugin <= 1.0.1 - Authenticated Arbitrary File Upload vulnerability

Authenticated (author or higher user role) Arbitrary File Upload vulnerability in ideasToCode Enable SVG, WebP & ICO Upload plugin <= 1.0.1 at WordPress.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects WordPress sites using ideasToCode Enable SVG, WebP & ICO Upload plugin version 1.0.1 or earlier. An authenticated Author-or-higher user could upload files the site should not accept. Impact can include loss of confidentiality, integrity, and availability, especially where contributor accounts are broadly issued or compromised.

Executive priority

Prioritize remediation for public WordPress sites, multi-author sites, and environments where account compromise would be plausible. This is high severity but not currently evidenced as actively exploited in the provided sources.

Technical view

CVE-2022-34154 is an authenticated arbitrary file upload issue, classified as CWE-434, in Enable SVG, WebP & ICO Upload <= 1.0.1. The CVSS 3.1 score is 7.2 with network attack vector, low complexity, high privileges required, no user interaction, and high CIA impact.

Likely exposure

Exposure is limited to WordPress sites with this specific plugin installed at version 1.0.1 or earlier, especially sites allowing Author-or-higher access to multiple users.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. Exploitation requires an authenticated account with Author-or-higher privileges, reducing reach but not impact if those accounts are compromised or externally assigned.

Researcher notes

Evidence identifies affected product, version boundary, CWE, CVSS vector, and authenticated role requirement. The bundle does not provide exploit details, fixed version, or operational indicators, so validation should focus on plugin presence, version, role exposure, and upload history.

Mitigation direction

  • Inventory WordPress sites for the affected plugin and version.
  • Check WordPress.org, vendor, or Patchstack guidance for a fixed version.
  • Disable or remove the plugin where no vendor-confirmed safe version is available.
  • Restrict Author-or-higher accounts to trusted users only.
  • Review recent uploads and privileged account activity on exposed sites.

Validation and detection

  • Confirm whether Enable SVG, WebP & ICO Upload is installed.
  • Verify installed plugin version is greater than 1.0.1 or otherwise vendor-confirmed safe.
  • List users with Author-or-higher roles on affected sites.
  • Review media uploads for unexpected file types or suspicious recent activity.
  • Check whether the site depends on this plugin before removal.
Prepared
Confidence
medium
Sources
4

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-2022-34154 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
3Source 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-2022-34154Attack 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
ideasToCodeEnable SVG, WebP & ICO Upload (WordPress plugin)<= 1.0.1Listed
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.