Themify Portfolio Post <= 1.1.5 - Authenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.1.6
- Affected Plugin
- Themify Portfolio Post
- Affected Version
<= 1.1.5- CVSS
- 5.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24129
At a glance
CVE-2021-24129 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Themify Portfolio Post WordPress plugin, affecting versions <= 1.1.5. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 1.1.6; sites on affected versions should update now. Disclosed December 2020, reported by Nguyen Anh Tien.
Vulnerability Overview
Unvalidated input and lack of output encoding in the Themify Portfolio Post WordPress plugin, versions before 1.1.6, lead to Stored Cross-Site Scripting (XSS) vulnerabilities allowing low-privileged users (Contributor+) to inject arbitrary JavaScript code or HTML in posts where the Themify Custom Panel is embedded, which could lead to privilege escalation.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Themify Portfolio Post <= 1.1.5 takes any authenticated account. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Themify Portfolio Post the fix is 1.1.6: builds <= 1.1.5 are affected, anything from 1.1.6 onward is not.
Remediation
Update to version 1.1.6, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Themify Portfolio Post: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Themify Portfolio Post 1.1.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Themify Portfolio Post
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C