CVE-2022-50970: WordPress Plugin AAWP 3.16 Reflected XSS via tab Parameter
WordPress Plugin AAWP 3.16 contains a reflected cross-site scripting vulnerability that allows authenticated attackers to inject malicious scripts by manipulating the tab parameter. Attackers can craft URLs with XSS payloads in the tab parameter of the aawp-settings admin page to execute arbitrary JavaScript in the context of authenticated users.
Security readout for executives and security teams
Plain-English summary
AAWP 3.16 for WordPress has a reflected cross-site scripting issue in its admin settings page. An authenticated attacker could craft a link that causes JavaScript to run in another logged-in user’s browser if that user opens it. Business impact is mainly account/session abuse or unauthorized actions within WordPress, not direct server takeover.
Executive priority
Handle during normal vulnerability remediation, with faster action for sites with many authenticated users or high-value WordPress administrator accounts. This is a meaningful web security issue, but the provided evidence does not support emergency response.
Technical view
The issue is CWE-79 reflected XSS in the AAWP settings admin page tab parameter. CVSS 3.1 is 5.4, with network access, low attack complexity, low privileges, and required user interaction. The scope is changed, with low confidentiality and integrity impact and no availability impact.
Likely exposure
Exposure is limited to WordPress sites running AAWP plugin version 3.16. Risk is higher where untrusted or lower-privileged authenticated users exist, or where administrators can be socially engineered into opening crafted URLs while logged in.
Exploitation context
The bundle references ExploitDB, so public exploit information exists. It is not listed in KEV, and the provided sources do not state active exploitation in the wild.
Researcher notes
Evidence identifies AAWP 3.16 and the tab parameter on the aawp-settings admin page. The sources do not name a fixed version, patch commit, or vendor mitigation. Treat remediation guidance as vendor-check-and-upgrade unless stronger vendor documentation is found.
Mitigation direction
Inventory WordPress sites for AAWP plugin version 3.16.
Check AAWP vendor guidance for a fixed release or mitigation.
Upgrade away from 3.16 when a vendor-supported fixed version is confirmed.
Limit WordPress administrative access to trusted users only.
Warn administrators not to open unsolicited WordPress admin links.
Validation and detection
Confirm whether AAWP is installed on each WordPress site.
Record the installed AAWP plugin version and compare it to 3.16.
Review who can access the AAWP settings admin page.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.