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

CVE-2026-57674

HIGH · 7.1 CVSS v3.1 Published 2026-07-02
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 7 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
Unauthenticated Cross Site Scripting (XSS) in Timetics <= 1.0.58 versions.

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

Unauthenticated stored Cross-Site Scripting (XSS) vulnerability in Timetics WordPress plugin versions 1.0.58 and below. An attacker can inject malicious JavaScript that executes in the browsers of users visiting the affected site, without requiring any authentication credentials.

MitigationUpdate Timetics to the latest version immediately; if no patched version is available, consider disabling the plugin until a fix is released. Sanitize and validate all user inputs on the affected endpoints.

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 Timetics plugin is installed
    Access your WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Timetics' in the list of active or inactive plugins.
    Affected if The Timetics plugin appears in the installed plugins list.
  2. Check the installed Timetics version
    In the Plugins list, click on 'Plugin Details' for Timetics or open the main plugin file (typically timetics.php) and locate the version declaration in the plugin header comment.
    Affected if The displayed version is 1.0.58 or lower.
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify whether Timetics shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin is currently activated on the WordPress site.
  4. Identify publicly accessible input points
    Review the Timetics plugin settings and frontend-facing pages (such as booking forms, calendar views, or scheduling endpoints) that do not require user login. These are the potential injection points for unauthenticated stored XSS.
    Affected if The plugin exposes any public-facing forms or input fields accessible without authentication.

You are affected if the Timetics plugin is installed, active, and running version 1.0.58 or lower, with publicly accessible input fields that accept user-supplied content.

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

Update Timetics to the latest version immediately; if no patched version is available, consider disabling the plugin until a fix is released. Sanitize and validate all user inputs on the affected endpoints.

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

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 locally
dbcve dependency scanner

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