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

CVE-2026-2834

HIGH · 7.2 CVSS v3.1 Published 2026-04-15
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

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 Age Verification & Identity Verification by Token of Trust plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘description’ parameter in all versions up to, and including, 3.32.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Age Verification & Identity Verification by Token of Trust WordPress plugin (versions up to 3.32.3) is vulnerable to stored Cross-Site Scripting (XSS) due to insufficient input sanitization and output escaping of the 'description' parameter. Unauthenticated attackers can inject arbitrary JavaScript or HTML into the description field, which will execute in the browsers of users who access affected pages.

MitigationUpdate the plugin to a version beyond 3.32.3, which should contain proper input sanitization using functions like sanitize_text_field() and output escaping using functions like esc_html() or esc_attr().

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. Confirm Token of Trust plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Age Verification & Identity Verification by Token of Trust' or check the plugins directory via file system for /wp-content/plugins/age-verification-id-verification-token-of-trust/
    Affected if Plugin is not installed means not affected
  2. Check installed plugin version
    View the plugin main file (usually age-verification-id-verification-token-of-trust.php) and look for the version number in the plugin header comment, or check in WordPress admin plugin list
    Affected if Version is 3.32.3 or lower (the affected range is versions up to and including 3.32.3)
  3. Identify if description field configuration exists
    Check plugin settings pages in WordPress admin under Token of Trust plugin options for any 'description' field configuration, or query the WordPress options database table for options containing 'description' related to this plugin
    Affected if The description field exists in plugin configuration and is accessible for modification
  4. Check for existing malicious payloads in description field
    Inspect the WordPress options database table (wp_options) for any stored description values containing script tags, iframe tags, or javascript: URIs, or view the plugin's description field settings in the admin panel for any suspicious content
    Affected if The description field contains unsanitized HTML/script tags indicating active exploitation

User is affected if the Token of Trust plugin versions up to 3.32.3 is installed AND the description field is configured with user-supplied content, particularly if unauthenticated access is possible to modify this field.

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 plugin to a version beyond 3.32.3, which should contain proper input sanitization using functions like sanitize_text_field() and output escaping using functions like esc_html() or esc_attr().

Recommended fix Moderate confidence

Latest version available on WordPress.org plugin repository (version higher than 3.32.3)

  1. Check the current version of the Age Verification & Identity Verification by Token of Trust plugin in your WordPress installation
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. If the installed version is 3.32.3 or lower, update the plugin to the latest available version from the WordPress plugin repository
  4. After updating, verify the plugin is running on a version higher than 3.32.3
  5. Test that the 'description' parameter properly escapes special characters and does not execute injected scripts

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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