dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-15298

HIGH · 7.2 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

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
The TelSender plugin for WordPress is vulnerable to DOM-Based Cross-Site Scripting in all versions up to, and including, 1.14.14. This is due to insufficient input sanitization when processing Telegram API responses containing attacker-controlled chat titles. This makes it possible for unauthenticated attackers to inject malicious scripts via Telegram chat titles that execute when an administrator opens the TelSender settings page and clicks the "Tested" button.

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

The TelSender WordPress plugin (versions up to 1.14.14) is vulnerable to DOM-based XSS due to insufficient sanitization of Telegram API responses. An unauthenticated attacker can inject malicious JavaScript into a Telegram chat title; when an administrator accesses the plugin settings page and clicks the 'Tested' button, the injected script executes in the admin's browser.

MitigationUpdate TelSender to the latest version beyond 1.14.14, which should include proper input sanitization and output encoding for Telegram chat title data. Alternatively, implement contextual output encoding and input validation before displaying any Telegram API response data.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Identify TelSender plugin installation
    In WordPress admin dashboard, navigate to Plugins > Installed Plugins and search for 'TelSender', or inspect the plugin directory at /wp-content/plugins/telsender/ for existence of plugin files
    Affected if TelSender plugin is present on the WordPress site
  2. Determine installed TelSender version
    In WordPress admin, go to Plugins > Installed Plugins > TelSender and read the version number displayed under the plugin name; alternatively, check the main plugin file (telsender.php) for the 'Version' header comment
    Affected if Version is 1.14.14 or lower (any version up to and including 1.14.14)
  3. Verify admin access to plugin settings
    Navigate to WordPress admin sidebar for TelSender settings page (typically under Settings or the plugin's own menu item); confirm the 'Tested' button exists on the settings interface
    Affected if Admin can access the plugin settings page with the 'Tested' button visible
  4. Check for Telegram API response handling
    Inspect plugin source code files for functions that process or display Telegram API responses, particularly chat title data; look for output statements that render chat title without visible sanitization
    Affected if Plugin processes and displays Telegram API response data on the settings page
  5. Confirm plugin is active
    In WordPress Plugins list, verify TelSender status shows as 'Active'; inactive plugins with vulnerable code are not exploitable in this attack chain
    Affected if TelSender plugin is activated on the WordPress site

User is affected if TelSender plugin versions up to 1.14.14 is installed and active, and an administrator with access to the plugin settings page exists who can trigger the 'Tested' button to render unsanitized Telegram chat title data.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update TelSender to the latest version beyond 1.14.14, which should include proper input sanitization and output encoding for Telegram chat title data. Alternatively, implement contextual output encoding and input validation before displaying any Telegram API response data.

Recommended fix Moderate confidence

TelSender version 1.14.15 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the TelSender plugin
  4. 4. Check if an update is available for TelSender
  5. 5. If update available, click 'Update Now' to install the latest version
  6. 6. After update, verify the plugin version is newer than 1.14.14
  7. 7. Test the TelSender settings page functionality to ensure proper operation

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15298 — 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-2026-15298 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