What is the CVSS score of CVE-2024-6847?

CVE-2024-6847 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.7%.

Is there a public PoC exploit available for CVE-2024-6847?

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

Chatbot With Chatgpt CVE-2024-6847

CRITICAL

SQL Injection (CWE-89)

2024-08-20 contact@wpscan.com

SQLi WordPress Chatbot With Chatgpt

9.8

CVSS 3.1 · Vendor: wpscan

Severity by source

Vendor (wpscan) PRIMARY

9.8 CRITICAL

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

Primary rating from Vendor (wpscan) · only source for this CVE.

CVSS VectorVendor: wpscan

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Aug 20, 2024 - 06:15 cve.org

CRITICAL 9.8

DescriptionCVE.org

AnalysisAI

The Chatbot with ChatGPT WordPress plugin before 2.4.5 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by unauthenticated. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as SQL Injection (CWE-89), which allows attackers to execute arbitrary SQL commands against the database. The Chatbot with ChatGPT WordPress plugin before 2.4.5 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by unauthenticated users when submitting messages to the chatbot. Affected products include: Webdigit Chatbot With Chatgpt. Version information: before 2.4.5.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use parameterized queries/prepared statements. Never concatenate user input into SQL. Apply least-privilege database permissions.