dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-53332

HIGH · 7.1 CVSS v3.1 Published 2025-06-27
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
Cross-Site Request Forgery (CSRF) vulnerability in ethoseo Track Everything track-everything allows Stored XSS.This issue affects Track Everything: from n/a through <= 2.0.1.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the ethoseo Track Everything WordPress plugin (version <= 2.0.1) allows attackers to trick authenticated administrators into submitting malicious requests that inject and store XSS payloads within the plugin's settings or tracked data, which then executes when other users view the affected content.

MitigationImplement anti-CSRF tokens and nonces for all state-changing operations, add proper input validation and output encoding/sanitization on all user-supplied data before storage and display. Consider disabling the plugin until a patched version is available.

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. Confirm plugin installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins. Locate 'ethoseo Track Everything' and note the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' tag.
    Affected if Plugin is installed and version is 2.0.1 or lower (no version shown, or version number <= 2.0.1)
  2. Identify plugin settings storage location
    Access the WordPress database (via phpMyAdmin or wp-cli). Query the wp_options table for option_name values containing 'ethoseo' or 'track_everything'. Common patterns: SELECT * FROM wp_options WHERE option_name LIKE '%ethoseo%' OR option_name LIKE '%track_everything%';
    Affected if Plugin options exist in the database, indicating the plugin has stored settings that could contain injected payloads
  3. Inspect stored settings for XSS indicators
    Review the option_value fields from the previous query. Look for common XSS patterns such as '<script', 'javascript:', 'onerror=', 'onload=', or encoded variants (&lt;script, etc.) within the stored values.
    Affected if Any option_value contains XSS payloads or suspicious HTML/script tags that were not intentionally configured by the administrator
  4. Check plugin settings pages in admin
    Visit the plugin settings page (typically under Settings > Track Everything or a dedicated ethoseo admin menu). View the page source or inspect form elements to see if user-supplied data is displayed without proper encoding.
    Affected if Plugin settings pages render stored data without sanitization, allowing injected scripts to execute in admin browser sessions

If the plugin is installed at version 2.0.1 or lower and any plugin-related options in the database contain unexpected script tags or XSS patterns, the environment is affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens and nonces for all state-changing operations, add proper input validation and output encoding/sanitization on all user-supplied data before storage and display. Consider disabling the plugin until a patched version is available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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