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

CVE-2026-6858

HIGH · 7.1 CVSS v3.1 Published 2026-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
The Transbank Webpay WordPress plugin before 1.14.0 does not sanitize and escape logs to be displayed, allowing unauthenticated users to perform Stored XSS attacks against logged in administrator

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 Transbank Webpay WordPress plugin before version 1.14.0 contains a stored XSS vulnerability where log data is displayed without proper sanitization or escaping. Unauthenticated attackers can inject malicious JavaScript through log entries that execute when viewed by logged-in administrators accessing the plugin's log display functionality.

MitigationUpdate the Transbank Webpay plugin to version 1.14.0 or later, which includes proper sanitization and escaping of log output. As an interim measure, limit administrative access and monitor for suspicious log entries.

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 checks

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

  1. Verify Transbank Webpay plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Transbank Webpay' or 'Transbank Webpay Oneclick' in the plugin list
    Affected if The plugin is not present in the plugin list (not affected)
  2. Check the installed plugin version
    In the Plugins list, click on the Transbank Webpay plugin to view its details, or inspect the plugin header in wp-content/plugins/transbank-webpay-oneclick/plugin.php to find the Version: x.x.x field
    Affected if The version number displayed is less than 1.14.0 (for example, 1.13.0, 1.12.0, etc.)
  3. Determine if log viewing is accessible
    Check if there is a log viewing interface in the WordPress admin panel under the Transbank Webpay settings or a dedicated logs section
    Affected if Log viewing functionality exists in the admin panel (required for the XSS to trigger)
  4. Inspect log entries for suspicious content
    If accessible, view the plugin logs and look for unusual JavaScript tags, script src attributes, or encoded characters that may indicate injected payloads
    Affected if Log entries contain unescaped HTML/script content that could execute in an admin browser

You are affected if the Transbank Webpay plugin is installed with a version lower than 1.14.0 AND the plugin has a log viewing feature accessible to administrators.

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 the Transbank Webpay plugin to version 1.14.0 or later, which includes proper sanitization and escaping of log output. As an interim measure, limit administrative access and monitor for suspicious log entries.

Recommended fix Moderate confidence

Transbank Webpay plugin version 1.14.0 or later

  1. Backup your WordPress site and database before making any changes
  2. Navigate to the WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Locate the 'Transbank Webpay' plugin
  5. Check the current version of the plugin - if it is below 1.14.0, it is vulnerable
  6. Update the plugin to version 1.14.0 or later via the WordPress plugin update mechanism
  7. Verify the update was successful by confirming the plugin version now shows 1.14.0 or higher
  8. Clear any server-side caches if used
Caveat Review plugin changelog for any configuration or compatibility changes between your current version and 1.14.0 before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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