Skip to main content

Chaty Pro EUVDEUVD-2026-49690

| CVE-2026-6251 MEDIUM
SQL Injection (CWE-89)
2026-07-28 Wordfence GHSA-h976-4r88-23hx
6.5
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain subscriber credentials
  2. Delivery
    Send crafted POST to admin endpoint
  3. Exploit
    SQL injection in fetch_custom_field()
  4. Execution
    Blind time-based extraction
  5. Impact
    Exfiltrate user credentials and config data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The attacker must have a valid WordPress user session with at least the Subscriber role. The vulnerable fetch_custom_field() function is triggered via an AJAX or admin POST request that includes the widget_id parameter; no additional plugin configuration is required. The nonce check occurs after the SQL query, so it does not prevent exploitation. The attack is limited to the network accessibility of the WordPress instance and the existence of subscriber accounts-common in many deployments.

Impact

The CVSS 3.1 base score is 6.5 (medium) with vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. This indicates a network-accessible, low-complexity attack requiring only subscriber-level authentication and no user interaction, leading to high confidentiality impact. No data on EPSS probability or CISA KEV status was provided; however, the lack of public exploit reports suggests limited active exploitation. The real-world risk is moderate: while authentication lowers the barrier compared to unauthenticated SQL injection, subscriber accounts are common and often poorly secured. The blind nature of the injection (time-based) may slow exploitation but does not reduce impact. Missing signals: EPSS and KEV data are unavailable; patch availability is inferred but not confirmed from the provided references.

Exploit ScenarioDerived

An authenticated attacker with a subscriber-level account submits a crafted POST request to the vulnerable Admin AJAX endpoint, injecting a time-based SQL payload into the widget_id parameter. The blind injection allows the attacker to enumerate sensitive data, such as user password hashes or WordPress configuration secrets, bit by bit over successive requests.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 28, 2026

SQL injection in the Chaty Pro WordPress plugin (up to version 3.5.5) allows authenticated attackers with subscriber-level access to extract sensitive database contents, including user credentials and configuration data. The vulnerability exists in the fetch_custom_field() function, which directly concatenates the widget_id POST parameter into a raw SQL query without using $wpdb->prepare(). No public exploit or active exploitation has been identified at the time of analysis, and the risk is elevated by the low privilege requirement.

RemediationAI

The primary remediation is to upgrade Chaty Pro to the latest version that includes a fix for this SQL injection. While the provided references do not specify a patched version, the vendor (Premio) typically releases updates; check the plugin changelog at https://plugins.trac.wordpress.org/browser/chaty-pro/ or the Wordfence advisory for the fixed version number. As a workaround, restrict subscriber-level privileges by ensuring only trusted users have accounts, or deploy a web application firewall (WAF) rule that blocks suspicious SQL patterns in the widget_id POST parameter. Note that blocking widget_id entirely may break legitimate chat functionality.

Affected VersionsENISA

Chaty Pro 0 ≤3.5.5

Affected Packages

euvd chaty_pro no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Chaty Pro is a premium WordPress plugin that provides live chat and customer communication features, written in PHP. The vulnerability is a classic SQL injection (CWE-89) arising from the fetch_custom_field() function in admin/class-admin-base.php. The function retrieves the widget_id parameter using filter_input(INPUT_POST, ...) and concatenates it directly into a SQL query within a numeric context, bypassing WordPress's built-in parameterized query methods ($wpdb->prepare()) and type casting. The nonce verification is performed after the query executes, rendering it ineffective. The affected CPE string cpe:2.3:a:chaty:chaty_pro:*:*:*:*:*:*:*:* indicates any version of Chaty Pro is potentially vulnerable.

Know when Chaty gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 6.5 MEDIUM

Requires subscriber-level authentication (PR:L); no user interaction; confidentiality impact only.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

The Chaty Pro plugin for WordPress is vulnerable to Authenticated Time-Based Blind SQL Injection in versions up to and including 3.5.5. This is due to the fetch_custom_field() function in admin/class-admin-base.php retrieving the widget_id POST parameter via filter_input(INPUT_POST, ...) and directly concatenating the value into a raw SQL query in a numeric context without using $wpdb->prepare() or any integer casting. Additionally, the nonce verification check is performed after the SQL query has already executed, providing no protection against the injection. This makes it possible for authenticated attackers with subscriber-level access and above to inject arbitrary SQL commands, potentially leading to unauthorized extraction of sensitive database contents including user credentials and configuration data.

Threat Intelligence Overview

EPSS Score
0.2%
Top 84% exploitable
Prevalence
Medium
Premium WordPress plugin, moderate adoption
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy