CVE-2025-28925
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Hieu Nguyen WATI Chat and Notification wati-chat-and-notification allows Stored XSS.This issue affects WATI Chat and Notification: from n/a through <= 1.1.2.
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 · moderate confidenceA CSRF vulnerability in the WATI Chat and Notification WordPress plugin (versions up to 1.1.2) allows attackers to trick authenticated administrators into submitting malicious requests that inject stored XSS payloads into the plugin's data. When other users view the affected content, the injected JavaScript executes in their browsers, enabling session hijacking or further compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Verify WATI Chat and Notification plugin is installedLog into WordPress admin, navigate to Plugins > Installed Plugins, and look for 'WATI Chat and Notification' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wati' or similar.Affected if The plugin appears in the installed plugins list
-
Check installed plugin versionIn WordPress admin, click on the plugin from the Plugins list to view its details, or inspect the main plugin PHP file (e.g., watichat-notification.php) and look for a version comment or defined constant.Affected if The version is 1.1.2 or any earlier version (the advisory states versions up to 1.1.2 are affected)
-
Identify plugin forms and AJAX endpointsReview the plugin files in /wp-content/plugins/ for PHP files containing form tags, $_POST or $_GET superglobal usage, and admin-ajax.php or admin_url() calls. Look for missing nonce verification (check for 'wp_verify_nonce' or 'nonce' in conditional logic).Affected if Plugin forms or AJAX handlers lack nonce verification or CSRF token validation
-
Inspect stored plugin data for malicious scriptsAccess the WordPress database (via phpMyAdmin or wp-cli) and query plugin-related tables. Look for unusual script tags, <script> elements, or JavaScript event handlers (onerror, onload, etc.) in fields that store plugin settings, messages, or notification content.Affected if Any stored XSS payloads (malicious JavaScript) are found in the plugin's database entries
A user is affected if the WATI Chat and Notification plugin (version 1.1.2 or earlier) is installed and contains forms or AJAX endpoints lacking CSRF protection, or if malicious scripts are already present in the plugin's stored data.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply available vendor patches; until then, disable the plugin or implement manual CSRF protection (nonces) on all plugin forms and AJAX endpoints, and ensure all stored data is properly sanitized before output.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28925 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-28925 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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