Google Drive
Approved changes feed: RSS · Atom
cpe:2.3:a:google:google_drive:2.2:*:*:*:*:*:*:*
part: a version: 2.2 update: *
| Vendor | Google (f181d1eb-7269-5bae-b76e-e66ceb214562) |
|---|---|
| Product | Google Drive (f8f52ec7-24d6-5a3c-97d3-f3bc7cc94d6e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-25326 |
vulnerable | 2026-06-08 05:11:29.795120 |
Google Drive for WordPress 2.2 Path Traversal RCE via gdrive-ajaxs.php
HIGH (7.5)
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.
Published: 2026-05-17T12:11:32.252Z
Updated: 2026-05-18T17:57:57.889Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.