CyberSecBulletin
CVE-2022-4949NVD status: Modified

AdSanity: Unrestricted Upload of File with Dangerous Type

CVE-2022-4949 is a high-severity unrestricted upload of file with dangerous type vulnerability in AdSanity from Https://adsanityplugin.com/, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 1.8.2 as the first without the flaw, so updating AdSanity to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 2.18% chance of exploitation within 30 days, higher than 83% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update AdSanity to 1.8.2 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
Https://adsanityplugin.com/AdSanitybefore 1.8.21.8.2
XenXenNot specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

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

Scoring systemScoreSeverityScored by
CVSS 3.18.8HighCNA (wordfence.com)
CVSS 3.18.8HighNVD

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Unrestricted Upload of File with Dangerous Type

The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.

How developers prevent this class of flaw

  • Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
  • When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
  • Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.

More Unrestricted Upload of File with Dangerous Type vulnerabilities (CWE-434)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Technical write-ups (may include proof of concept)

Recent Unrestricted Upload of File with Dangerous Type vulnerabilities

Spotted an error? Tell us.