CVE-2026-5114 MEDIUM

CVE-2026-5114: SpeedyCache <= 1.3.8 - Authenticated (Administrator+) Arbitrary File Read

Vendor Softaculous
Product SpeedyCache – Cache, Optimization, Performance
Weakness CWE-22 · Path traversal
Published July 28, 2026
Last update July 29, 2026

CVSS base score

4.9/10
Attack vector Network
Attack complexity Low
Privileges required High
User interaction None
Confidentiality High
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

What the vulnerability does

01Description

The SpeedyCache plugin for WordPress is vulnerable to Arbitrary File Read via Path Traversal in all versions up to, and including, 1.3.8. This is due to a mismatch between CSS URL validation (which allows query strings like `.css?...`) and path resolution (which strips query strings), combined with no validation that the resolved file is actually a CSS file. This makes it possible for authenticated attackers, with Administrator-level access and above, to read arbitrary files from the server (including `wp-config.php` and `/etc/passwd`) by injecting crafted `<link>` tags into page content, with the file contents written to publicly accessible cache files.

Explanation of Vulnerability in Simple Terms

02Summary

SpeedyCache versions up to 1.3.8 contain a path traversal vulnerability that allows high-privilege users to read arbitrary files from the server. An attacker with admin or equivalent access can bypass directory restrictions and access sensitive files outside the intended cache directory. This affects confidentiality but not data integrity or availability.

What an attacker can do

03Attacker Capabilities

Read arbitrary files on the server outside the cache directory.

Potential impact on your site

04Site Impact

Admins or compromised admin accounts can access sensitive files like configuration files, database credentials, or other private data.

Conditions required to exploit

05Prerequisites

Attacker must have high-level privileges (admin or equivalent role) on the site.

Key dates

06Disclosure timeline

July 28, 2026 CVE published
July 29, 2026 Record updated

Related vulnerabilities

08Related CVE