- Joined
- Mar 6, 2017
- Messages
- 3,385 (1.13/day)
- Location
- North East Ohio, USA
| System Name | My Ryzen 7 7700X Super Computer |
|---|---|
| Processor | AMD Ryzen 7 7700X |
| Motherboard | Gigabyte B650 Aorus Elite AX |
| Cooling | DeepCool AK620 with Arctic Silver 5 |
| Memory | 2x16GB G.Skill Trident Z5 NEO DDR5 EXPO (CL30) |
| Video Card(s) | XFX AMD Radeon RX 7900 GRE |
| Storage | Samsung 980 EVO 1 TB NVMe SSD (System Drive), Samsung 970 EVO 500 GB NVMe SSD (Game Drive) |
| Display(s) | Acer Nitro XV272U (DisplayPort) and Acer Nitro XV270U (DisplayPort) |
| Case | Lian Li LANCOOL II MESH C |
| Audio Device(s) | On-Board Sound / Sony WH-XB910N Bluetooth Headphones |
| Power Supply | MSI A850GF |
| Mouse | Logitech M705 |
| Keyboard | Steelseries |
| Software | Windows 11 Pro 64-bit |
| Benchmark Scores | https://valid.x86.fr/liwjs3 |
I was browsing through the Wordfence Web Application Firewall log of my Wordpress site, and I found something interesting. Thankfully it was blocked by Wordfence so that's good—it never did any damage to my site. I don't even have the plugin installed on my site so again, good.
However, I digress—I found an exploit in an old Wordpress plugin. So old that it doesn't seem that Wordpress even lists it as a plugin to be installed. Thankfully.
However, the plugin does exist. I found it on Github and after a little bit of investigation, one of the files in that plugin is indeed vulnerable to that very exploit. A path traversal exploit. There's no input validation or cleanup before passing it to a PHP read() function.
What do I do with this knowledge? Is there a possibility that sites out there have this plugin installed and are vulnerable to this exploit?
Obviously, I don't want to publish this exploit or the name of the plugin publicly since well... duh. But what do I do? I have no idea how to responsibly disclose this vulnerablity.
However, I digress—I found an exploit in an old Wordpress plugin. So old that it doesn't seem that Wordpress even lists it as a plugin to be installed. Thankfully.
However, the plugin does exist. I found it on Github and after a little bit of investigation, one of the files in that plugin is indeed vulnerable to that very exploit. A path traversal exploit. There's no input validation or cleanup before passing it to a PHP read() function.
What do I do with this knowledge? Is there a possibility that sites out there have this plugin installed and are vulnerable to this exploit?
Obviously, I don't want to publish this exploit or the name of the plugin publicly since well... duh. But what do I do? I have no idea how to responsibly disclose this vulnerablity.
