CVE-2019-15648

Insert or Embed Articulate Content into WordPress < 4.29991 - Directory Traversal

2019-07-02 00:00
WPScanTeam

Strategic Overview

Status
Patched in 4.29991
Affected Plugin
Insert or Embed Articulate Content into WordPress
Affected Version
< 4.29991
CVSS
6.5Medium
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2019-15648
View all Insert or Embed Articulate Content into WordPress vulnerabilities

At a glance

CVE-2019-15648 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Insert or Embed Articulate Content into WordPress WordPress plugin, affecting versions < 4.29991. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity impact). The issue is fixed in version 4.29991; sites on affected versions should update now. Disclosed July 2019, reported by WPScanTeam.

Vulnerability Overview

The Insert or Embed Articulate Content into WordPress plugin for WordPress is vulnerable to Directory Traversal in versions up to, and including, 4.2999 via the rename_dir. This allows authenticated user with a role as low as subscriber to delete and rename arbitrary folders.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on integrity.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in Insert or Embed Articulate Content into WordPress < 4.29991 takes a caller who can reach the endpoint. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Insert or Embed Articulate Content into WordPress the fix is 4.29991: builds < 4.29991 are affected, anything from 4.29991 onward is not.

Remediation

Update to version 4.29991, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Insert or Embed Articulate Content into WordPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Insert or Embed Articulate Content into WordPress 4.29991 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2019-15648https://www.wordfence.com/threat-intel/vulnerabilities/id/1c225bea-78db-4f4c-a201-833436c1df78https://nvd.nist.gov/vuln/detail/CVE-2019-15648

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C