In affected versions of WordPress, authenticated users with upload permissions (like authors) are able to inject JavaScript into some media…
In affected versions of WordPress, authenticated users with upload permissions (like authors) are able to inject JavaScript into some media file attachment pages in a certain way. This can lead to script execution in the context of a higher privileged user when the file is viewed by them. This has been patched in version 5.4.2, along with all the previously affected versions via a minor release (5.3.4, 5.2.7, 5.1.6, 5.0.10, 4.9.15, 4.8.14, 4.7.18, 4.6.19, 4.5.22, 4.4.23, 4.3.24, 4.2.28, 4.1.31, 4.0.31, 3.9.32, 3.8.34, 3.7.34).
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.
https://cwe.mitre.org/data/definitions/80.html →Open in CWE collection →This attack is a form of Cross-Site Scripting (XSS) where malicious scripts are embedded in elements that are not expected to host scripts such as image tags (<img>), comments in XML documents (< !-CDATA->), etc. These tags may not be subject to the same input validation, output validation, and other content filtering and checking routines, so this can create an opportunity for an adversary to tunnel through the application's elements and launch a XSS attack through other elements. As with all remote attacks, it is important to differentiate the ability to launch an attack (such as probing an internal network for unpatched servers) and the ability of the remote adversary to collect and interpret the output of said attack.
https://capec.mitre.org/data/definitions/18.html →Open in CAPEC collection →An adversary embeds malicious script code in the parameters of an HTTP query string and convinces a victim to submit the HTTP request that contains the query string to a vulnerable web application. The web application then procedes to use the values parameters without properly validation them first and generates the HTML code that will be executed by the victim's browser.
https://capec.mitre.org/data/definitions/32.html →Open in CAPEC collection →An adversary exploits web applications that generate web content, such as links in a HTML page, based on unvalidated or improperly validated data submitted by other actors. XSS in HTTP Headers attacks target the HTTP headers which are hidden from most users and may not be validated by web applications.
https://capec.mitre.org/data/definitions/86.html →Open in CAPEC collection →In this pattern the adversary is able to load and execute arbitrary code remotely available from the application. This is usually accomplished through an insecurely configured PHP runtime environment and an improperly sanitized "include" or "require" call, which the user can then control to point to any web-accessible file. This allows adversaries to hijack the targeted application and force it to execute their own instructions.
https://capec.mitre.org/data/definitions/193.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| wordpress | Tracked | |
| debian_linux | * | Tracked |
| fedora | * | Tracked |
| wordpress | * | Tracked |