CVE-2026-13339

CubeWP Framework <= 1.1.30 - Unauthenticated Arbitrary File Read via prev_icon/next_icon Parameter

2026-08-01 10:44
Nhien Pham (nhienit) (nhienit)

Strategic Overview

Status
Patched in 1.1.31
Affected Plugin
CubeWP Framework
Affected Version
<= 1.1.30
CVSS
7.5High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2026-13339
View all CubeWP Framework vulnerabilities

At a glance

CVE-2026-13339 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the CubeWP Framework WordPress plugin, affecting versions <= 1.1.30. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 1.1.31; sites on affected versions should update now. Disclosed August 2026, reported by Nhien Pham (nhienit) (nhienit).

Vulnerability Overview

The CubeWP Framework plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.1.30 via the 'cubewp_get_svg_content' function. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. This is exploitable by unauthenticated attackers because the required nonce is publicly emitted into the markup of any page rendering the CubeWP posts shortcode or widget with AJAX loading enabled, making it harvestable by any guest visitor before submitting the AJAX request.

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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

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

CubeWP Framework <= 1.1.30 carries this weakness at cubewp_get_svg_content, and reaching it takes no account at all. 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 CubeWP Framework the fix is 1.1.31: builds <= 1.1.30 are affected, anything from 1.1.31 onward is not.

Remediation

Update to version 1.1.31, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: CubeWP Framework 1.1.31 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-13339https://www.wordfence.com/threat-intel/vulnerabilities/id/7ea72320-0e1e-45e3-987d-9ab7eecf1aeehttps://nvd.nist.gov/vuln/detail/CVE-2026-13339

Related records

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