Vulnerabilities

Vulnerability · CVE-2025-10701

The Time Clock – A WordPress Employee & Volunteer Time Clock Plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data' parameter in all versions up to, and i

Published Oct 24, 2025 · catalog updated Apr 8, 2026 · Time Clock – A WordPress Employee & Volunteer Time Clock Plugin

Last checked Oct 30, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-10701. EPSS is 0.24%. Act only if a listed version of Time Clock – A WordPress Employee & Volunteer Time Clock Plugin is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium6.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.24%
Remediation
Vendor / distro source
Affected products
vendor scottpaterson Time Clock – A WordPress Employee & Volunteer Time Clock Plugin 0 ≤1.3.1

The Time Clock – A WordPress Employee & Volunteer Time Clock Plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data' parameter in all versions up to, and including, 1.3.1. This is due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with Time Clock user credentials to inject arbitrary web scripts in pages that will execute whenever a user accesses an affected page.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor scottpaterson Time Clock – A WordPress Employee & Volunteer Time Clock Plugin 0 ≤1.3.10 ≤1.3.1

How to fix CVE-2025-10701

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-10701. EPSS is 0.24%. Act only if a listed version of Time Clock – A WordPress Employee & Volunteer Time Clock Plugin is installed.

Which versions are affected?

Compare what you have installed with scottpaterson Time Clock – A WordPress Employee & Volunteer Time Clock Plugin 0 ≤1.3.1 0 ≤1.3.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.24%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 24, 2025 · EUVD

    Detected

    The Time Clock – A WordPress Employee & Volunteer Time Clock Plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data' parameter in all versions up to, and including, 1.3.1. This is due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with Time Clock user credentials to inject arbitrary web

  2. Apr 8, 2026 · EUVD

    Updated

    The Time Clock – A WordPress Employee & Volunteer Time Clock Plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data' parameter in all versions up to, and including, 1.3.1. This is due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with Time Clock user credentials to inject arbitrary web

Sources

  • CVE.orgVulnerability recordCVE-2025-10701

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-10701

    30-day exploitation probability 0.24%

    first.org
  • EUVDVulnerability recordEUVD-2025-35818

    The Time Clock – A WordPress Employee & Volunteer Time Clock Plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data' parameter in all versions up to, and including, 1.3.1. This is due to insufficient input sanitization and output escaping on user supplied

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Oct 30, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 30, 2026
  • CVE.orgOct 24, 2026
  • EUVDOct 24, 2026