GridKit Portfolio <= 2.0.0 - Subscriber+ Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.1.0
- Affected Plugin
- Portfolio, Gallery, Product Catalog – Grid KIT Portfolio
- Affected Version
< 2.1.0- CVSS
- 5.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-25090
At a glance
CVE-2021-25090 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Portfolio, Gallery, Product Catalog WordPress plugin, affecting versions < 2.1.0. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The issue is fixed in version 2.1.0; sites on affected versions should update now. Disclosed March 2022, reported by Krzysztof Zając.
Vulnerability Overview
The Portfolio Gallery, Product Catalog WordPress plugin before 2.1.0 does not have authorisation and CSRF checks in various functions related to AJAX actions, allowing any authenticated users, such as subscriber, to call them. Due to the lack of sanitisation and escaping, it could also allows attackers to perform Cross-Site Scripting attacks on pages where a Portfolio is embed
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 Portfolio, Gallery, Product Catalog < 2.1.0 takes a caller who can reach the endpoint. 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 Portfolio, Gallery, Product Catalog the fix is 2.1.0: builds < 2.1.0 are affected, anything from 2.1.0 onward is not.
Remediation
Update to version 2.1.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Portfolio, Gallery, Product Catalog: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Portfolio, Gallery, Product Catalog 2.1.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C