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

CVE-2021-24772 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 1.5%.

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

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

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

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

Stream CVE-2021-24772

HIGH

SQL Injection (CWE-89)

2021-11-17 contact@wpscan.com

WordPress SQLi Stream

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Nov 17, 2021 - 11:15 nvd

HIGH 8.8

DescriptionNVD

AnalysisAI

The Stream WordPress plugin before 3.8.2 does not sanitise and validate the order GET parameter from the Stream Records admin dashboard before using it in a SQL statement, leading to an SQL injection. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as SQL Injection (CWE-89), which allows attackers to execute arbitrary SQL commands against the database. The Stream WordPress plugin before 3.8.2 does not sanitise and validate the order GET parameter from the Stream Records admin dashboard before using it in a SQL statement, leading to an SQL injection issue. Affected products include: Xwp Stream. Version information: before 3.8.2.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use parameterized queries/prepared statements. Never concatenate user input into SQL. Apply least-privilege database permissions.