CVE-2013-6880

Time Sheets <= 2.1.3 - Use of Known Vulnerable Component

Strategic Overview

Status
Unpatched
Affected Plugin
Time Sheets
Affected Version
<= 2.1.3
CVSS
7.2High
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2013-6880
View all Time Sheets vulnerabilities

At a glance

CVE-2013-6880 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Time Sheets WordPress plugin, affecting versions <= 2.1.3. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed December 2025, reported by Athiwat Tiprasaharn (Jitlada).

Vulnerability Overview

The Time Sheets plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.1.3. This is due to the plugin using a vulnerable package of FlashCanvas and FlashCanvasPro. This makes it possible for unauthenticated attackers to make arbitrary requests to internal services.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in Time Sheets <= 2.1.3 takes a caller who can reach the endpoint. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. No fixed build of this plugin is recorded for Time Sheets yet, so installs running <= 2.1.3 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

The attempt arrives as an ordinary request to Time Sheets: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C