CVE-2018-25326 Google Drive for WordPress 2.2 Path Traversal RCE via gdrive-ajaxs.php

High 8.7 Published Updated

Unauthenticated attackers can read arbitrary files, including sensitive configuration files, via path traversal in the Google Drive for WordPress plugin.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2018-25326?

CVE-2018-25326 is a high-severity path traversal vulnerability in wp-google-drive Google Drive, published on 17 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

Google Drive for WordPress 2.2 contains a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files by injecting directory traversal sequences in the file_name parameter. Attackers can send POST requests to gdrive-ajaxs.php with the ajaxstype parameter set to del_fl_bkp and file_name containing traversal sequences ../../wp-config.php to access sensitive configuration files.

Weakness: CWE-22

Which versions are affected by CVE-2018-25326?

How do I fix CVE-2018-25326?

No fix has been published for CVE-2018-25326 yet. Limit exposure of the affected software until one is available.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2018-25326 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25326 exists.

Sources

Also known as GHSA-3rwr-mwr8-225x.

Is CVE-2018-25326 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free