CVE-2025-10701 MEDIUM

CVE-2025-10701: Time Clock – A WordPress Employee & Volunteer Time Clock Plugin <= 1.3.1 - Authenticated (Custom+) Stored Cross-Site Scripting

Vendor Scottpaterson
Product Time Clock – A WordPress Employee & Volunteer Time Clock Plugin
Weakness CWE-79 · XSS
Published October 24, 2025
Last update April 8, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

The Time Clock plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in versions up to 1.3.1. An authenticated user with low privileges can inject malicious scripts that execute in the browsers of other site users, including administrators. The vulnerability affects the entire site due to scope change, allowing attackers to steal session tokens, modify content, or perform actions on behalf of victims.

What an attacker can do

03Attacker Capabilities

Inject malicious scripts that run in other users' browsers and execute site actions on their behalf.

Potential impact on your site

04Site Impact

Authenticated attackers can compromise admin accounts, steal data, or modify site content via injected scripts.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress account (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

October 24, 2025 CVE published
April 8, 2026 Record updated