CyberSecBulletin
CVE-2022-2261NVD status: Modified

WPIDE – File Manager & Code Editor: Improper Limitation of a Pathname to a Restricted Directory

Published Updated By the CyberSecBulletin desk

CVE-2022-2261 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in WPIDE – File Manager & Code Editor, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists version 3.0 as the first without the flaw, so updating WPIDE – File Manager & Code Editor to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.46% chance of exploitation within 30 days, higher than 74% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update WPIDE – File Manager & Code Editor to 3.0 or a later version.
  2. Update Wpide to 3.0 or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
WPIDE – File Manager & Code EditorWPIDE – File Manager & Code Editor3.0 up to, but not including, 3.03.0
XplodedthemesWpidebefore 3.03.0

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
HighAdministrator-level access is required first.
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:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Official description

The WPIDE WordPress plugin before 3.0 does not sanitize and validate the filename parameter before using it in a require statement in the admin dashboard, leading to a Local File Inclusion issue.

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

The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

How developers prevent this class of flaw

  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.

More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)

Timeline

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

References

Technical write-ups (may include proof of concept)

Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities

Spotted an error? Tell us.