LiveActive security incident?Get immediate response
CVE Record

CVE-2022-4949: AdSanity < 1.8.2 - Authenticated Arbitrary File Upload

The AdSanity plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'ajax_upload' function in versions up to, and including, 1.8.1. This makes it possible for authenticated attackers with Contributor+ level privileges to upload arbitrary files on the affected sites server which makes remote code execution possible.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A vulnerable AdSanity WordPress plugin version can let a logged-in Contributor or higher upload files the server should reject. If abused, this can lead to full site compromise, including data theft, content changes, or service disruption.

Executive priority

Treat this as a high-priority WordPress plugin issue because authenticated compromise can become full server-side code execution. Prioritize public sites and sites with many content contributors.

Technical view

CVE-2022-4949 is a CWE-434 arbitrary file upload flaw in AdSanity through 1.8.1. The reported issue is missing file type validation in the ajax_upload function, allowing authenticated Contributor+ users to upload arbitrary files, making remote code execution possible.

Likely exposure

Exposure is limited to WordPress sites running AdSanity versions up to and including 1.8.1, especially where Contributor-level accounts are available to untrusted users or compromised accounts.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. Practical abuse requires authenticated Contributor+ WordPress access, but the impact can be severe once that access exists.

Researcher notes

Key evidence is the CVE description and Wordfence/Nintechnet references. The source bundle includes unrelated transferred Xen references; they should not be used to infer AdSanity impact or remediation.

Mitigation direction

  • Update AdSanity to 1.8.2 or later after checking vendor guidance.
  • Remove or reduce Contributor+ access for users who do not need it.
  • Audit recent uploads and plugin directories for unexpected files.
  • Disable or remove AdSanity where it is not business-critical.
  • Review WordPress account security and reset suspicious credentials.

Validation and detection

  • Inventory all WordPress sites for installed AdSanity versions.
  • Confirm no site runs AdSanity 1.8.1 or earlier.
  • Review Contributor, Author, Editor, and Administrator accounts for legitimacy.
  • Check web server logs for unusual authenticated upload activity.
  • Inspect uploaded files for unexpected executable or script content.
Prepared
Confidence
high
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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-4949 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
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-4949Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
https://adsanityplugin.com/AdSanity0unaffected
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.