dbcve.org
ChatyWordPress extension · Premio

CVE-2023-25019

MEDIUM · 6.1 CVSS v3.1 Published 2023-08-30
Fix available
A fix is available. Upgrade to after 3.0.9 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Premio Chaty plugin <= 3.0.9 versions

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Unauthenticated reflected Cross-Site Scripting (XSS) vulnerability in the Premio Chaty WordPress plugin affecting versions 3.0.9 and earlier. Attackers can inject malicious JavaScript through unsanitized user input that gets reflected back in the web page, potentially stealing session cookies or performing actions on behalf of users.

MitigationUpdate Premio Chaty plugin to the latest version (3.1 or later) to patch the XSS vulnerability. If immediate update is not possible, disable the plugin or deploy WAF rules to filter malicious XSS payloads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChatyWordPress extension
Affected:<= 3.0.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Premio Chaty plugin is installed
    Log into WordPress admin, navigate to Plugins > Installed Plugins, and look for 'Premio Chaty' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'chaty' or 'premio-chaty'.
    Affected if Premio Chaty plugin is not found in the installed plugins list or the plugins directory.
  2. Check the installed version number
    In WordPress admin, find Premio Chaty in the Plugins list and view the version number under the plugin name. If using WP-CLI, run: wp plugin list --name='premio-chaty' --format=table
    Affected if The version listed is 3.0.9 or any earlier version (3.0.0 through 3.0.9).
  3. Confirm the plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that Premio Chaty shows as 'Active' (not just installed but deactivated).
    Affected if Premio Chaty is active. Reflected XSS requires the plugin to be actively handling requests to be exploitable.
  4. Identify exposed endpoints accepting user input
    Review the plugin's frontend functionality. Premio Chaty typically adds a chat widget to sites. Check for URL parameters that might reflect user input (common XSS vectors like ?chaty=, ?preview=, or custom query params). Examine page source of any page loading the chat widget.
    Affected if The plugin processes and reflects user-supplied input back into the HTML output without sanitization.

A user is affected if the Premio Chaty WordPress plugin is installed, active, and running version 3.0.9 or earlier, exposing reflected XSS via endpoints that echo user input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.0.9
Interim mitigation

Update Premio Chaty plugin to the latest version (3.1 or later) to patch the XSS vulnerability. If immediate update is not possible, disable the plugin or deploy WAF rules to filter malicious XSS payloads.

Recommended fix Moderate confidence

Chaty 3.1.0 or later (check wordpress.org for latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Chaty plugin in the list
  4. If the current version is 3.0.9 or earlier, click Update Now to upgrade to the latest version
  5. Alternatively, navigate to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chaty Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA0.5 h
3.5 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-25019 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-25019 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data