CVE-2026-7558
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 · uneditedThe Age Verification & Identity Verification by Token of Trust plugin for WordPress is vulnerable to unauthorized access in all versions up to and including 4.0.2. This is due to the handle_export_table() function being registered on the WordPress 'init' hook, which fires for all requests, including those from unauthenticated visitors, without any capability check. This makes it possible for unauthenticated attackers to download a CSV file containing sensitive WooCommerce donation data, including order dates, order IDs, charitable donation amounts, and admin-only order edit URLs, simply by visiting any page on the site with the 'tot_export_table' GET parameter set to a numeric value (0–3).
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 confidenceThe Token of Trust plugin registers handle_export_table() on WordPress's 'init' hook without capability verification, allowing any visitor to export sensitive WooCommerce donation data (order IDs, amounts, dates, admin URLs) by adding the 'tot_export_table' GET parameter (values 0-3) to any page URL.
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
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Token of Trust plugin is installedCheck your WordPress plugins directory for the 'token-of-trust' folder or look for 'Token of Trust' in the Plugins admin pageAffected if The plugin folder 'token-of-trust' exists in wp-content/plugins/ or the plugin appears in your WordPress plugins list
-
Locate handle_export_table functionSearch plugin files for 'function handle_export_table' or 'handle_export_table()' using grep, grep -r "handle_export_table" wp-content/plugins/token-of-trust/ or a file searchAffected if The function is found in the plugin codebase
-
Check if function is hooked to 'init' without capability checkSearch for add_action('init' or add_action("init" and examine whether 'manage_options' or capability check appears before handle_export_table is calledAffected if add_action('init', 'handle_export_table') exists without a preceding current_user_can() check in the same file or function
-
Test if export parameter is acceptedAdd '?tot_export_table=1' or '?tot_export_table=0' to any URL on your site (e.g., example.com/?tot_export_table=1) and observe if a CSV download triggers or donation data appearsAffected if Requesting any page with tot_export_table=0,1,2, or 3 triggers a file download or displays sensitive data without authentication
-
Check for WooCommerce donation data exposureIf the export triggers, examine the downloaded file or output for WooCommerce order IDs, amounts, dates, and admin URLsAffected if The exported data contains WooCommerce order information including amounts and dates without logging in
Your environment is affected if the Token of Trust plugin is installed AND the handle_export_table function is hooked to 'init' without a capability check, allowing unauthenticated access via the tot_export_table GET parameter.
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 dataAdd a capability check (e.g., current_user_can('manage_options')) at the start of handle_export_table() to restrict access to administrators only, or move the function to an admin-only hook.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7558 — 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-2026-7558 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