Absolutely Glamorous Custom Admin <= 6.8 - Authenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 6.9
- Affected Plugin
- AGCA – Custom Dashboard & Login Page
- Affected Version
<= 6.8- CVSS
- 6.6Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-36823
At a glance
CVE-2021-36823 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the AGCA WordPress plugin, affecting versions <= 6.8. It carries a CVSS score of 6.6 (reachable over the network; low attack complexity). Exploitation requires an authenticated account. The issue is fixed in version 6.9; sites on affected versions should update now. Disclosed September 2021, reported by Jorgson.
Vulnerability Overview
Authenticated Stored Cross-Site Scripting (XSS) vulnerability in WordPress Absolutely Glamorous Custom Admin plugin (versions <= 6.8). Stored XSS possible via unsanitized input fields of the plugin settings, some of the payloads could make the frontend and the backend inaccessible.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in AGCA <= 6.8 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 AGCA the fix is 6.9: builds <= 6.8 are affected, anything from 6.9 onward is not.
Remediation
Update to version 6.9, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to AGCA: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: AGCA 6.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in AGCA – Custom Dashboard & Login Page
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C