Skip to content
Fencer Intel
medium 6.1

CVE-2024-6651 json

WordPress File Upload < 4.24.8 - Reflected XSS

published 2y ago modified 4mo ago also EUVD-2024-47708

cvss
6.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
15.7%
EPSS 15.7% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

The WordPress File Upload WordPress plugin before 4.24.8 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin

Patch / fix

  • Unknown WordPress File Upload 4.24.8
  • wordpress_file_upload_project wordpress_file_upload 4.24.8

Is CVE-2024-6651 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

15.66% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • wpscan.com https://wpscan.com/vulnerability/65e2c77d-09bd-4a44-81d9-d7a5db0e0f84/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
CNA 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected products

  • Unknown WordPress File Upload
  • wordpress_file_upload_project wordpress_file_upload

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.