What is the CVSS score of CVE-2021-24830?

CVE-2021-24830 has a CVSS 3.1 base score of 4.8 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.7%.

Is there a public PoC exploit available for CVE-2021-24830?

Yes, a public proof-of-concept exploit is available for CVE-2021-24830. Prioritise patching immediately. EPSS: 0.7%.

Is there a patch available for CVE-2021-24830?

Yes, a patch is available for CVE-2021-24830. Update the affected software to the latest version immediately.

Advanced Access Manager CVE-2021-24830

MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2021-11-23 contact@wpscan.com

WordPress XSS Advanced Access Manager

4.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

4.8 MEDIUM

AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

CVE Published

Nov 23, 2021 - 20:15 nvd

MEDIUM 4.8

DescriptionNVD

The Advanced Access Manager WordPress plugin before 6.8.0 does not escape some of its settings when outputting them, allowing high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed

AnalysisAI

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. The Advanced Access Manager WordPress plugin before 6.8.0 does not escape some of its settings when outputting them, allowing high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed Affected products include: Vasyltech Advanced Access Manager. Version information: before 6.8.0.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.