CVE-2022-24707

HIGHNVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 7.2% (94th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.4EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 7.2%CVSS: 7.4Exploit: Elevated riskExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Anuko Time Tracker is an open source, web-based time tracking application written in PHP. UNION SQL injection and time-based blind injection vulnerabilities existed in Time Tracker Puncher plugin in versions of anuko timetracker prior to 1.20.0.5642. This was happening because the Puncher plugin was reusing code from other places and was relying on an unsanitized date parameter in POST requests. Because the parameter was not checked, it was possible to craft POST requests with malicious SQL for Time Tracker database. This issue has been resolved in in version 1.20.0.5642. Users unable to upgrade are advised to add their own checks to input.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
7.2%
EPSS %ILE
94th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 24, 2022

Last Modified

November 21, 2024

References (6)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 162 total refreshes for this CVE.

  1. 2026-10-05 17:40 UTCEPSS rescore
  2. 2026-10-04 23:19 UTCEPSS rescore
  3. 2026-10-03 14:23 UTCEPSS rescore
  4. 2026-10-03 14:22 UTCEPSS rescore
  5. 2026-09-30 15:51 UTCEG score recompute
  6. 2026-09-30 15:00 UTCEPSS rescore
  7. 2026-09-29 15:15 UTCEPSS rescore
  8. 2026-09-28 13:48 UTCEPSS rescore
  9. 2026-09-27 13:41 UTCEPSS rescore
  10. 2026-09-26 00:22 UTCEPSS rescore
  11. 2026-09-25 04:54 UTCOSV refresh
  12. 2026-09-24 14:00 UTCEPSS rescore
  13. 2026-09-23 13:45 UTCEPSS rescore
  14. 2026-09-17 19:23 UTCEPSS rescore
  15. 2026-09-16 14:05 UTCEPSS rescore
  16. 2026-09-15 03:06 UTCEPSS rescore
  17. 2026-09-13 16:43 UTCEPSS rescore
  18. 2026-09-12 14:57 UTCEPSS rescore
  19. 2026-09-11 14:49 UTCEPSS rescore
  20. 2026-09-11 09:33 UTCEPSS rescore
  21. 2026-09-08 21:57 UTCEPSS rescore
  22. 2026-09-07 15:58 UTCEPSS rescore
  23. 2026-09-06 13:45 UTCEPSS rescore
  24. 2026-09-05 20:51 UTCOSV refresh
  25. 2026-09-05 15:25 UTCEPSS rescore
Show 75 more
  1. 2026-09-04 13:57 UTCEPSS rescore
  2. 2026-09-04 05:04 UTCEPSS rescore
  3. 2026-09-02 14:09 UTCEPSS rescore
  4. 2026-09-01 13:51 UTCEPSS rescore
  5. 2026-08-30 19:14 UTCEPSS rescore
  6. 2026-08-30 01:19 UTCEPSS rescore
  7. 2026-08-28 21:38 UTCEPSS rescore
  8. 2026-08-27 14:22 UTCEPSS rescore
  9. 2026-08-26 14:43 UTCEPSS rescore
  10. 2026-08-25 13:46 UTCEPSS rescore
  11. 2026-08-25 13:46 UTCEPSS rescore
  12. 2026-08-24 14:13 UTCEPSS rescore
  13. 2026-08-21 23:46 UTCEPSS rescore
  14. 2026-08-20 22:52 UTCEPSS rescore
  15. 2026-08-19 17:01 UTCEPSS rescore
  16. 2026-08-19 07:32 UTCOSV refresh
  17. 2026-08-18 13:45 UTCEPSS rescore
  18. 2026-08-16 14:53 UTCEPSS rescore
  19. 2026-08-16 02:11 UTCEPSS rescore
  20. 2026-08-15 01:27 UTCEPSS rescore
  21. 2026-08-13 21:57 UTCEPSS rescore
  22. 2026-08-12 13:48 UTCEPSS rescore
  23. 2026-08-09 13:44 UTCEPSS rescore
  24. 2026-08-08 16:34 UTCEPSS rescore
  25. 2026-08-07 16:24 UTCEPSS rescore
  26. 2026-08-06 13:44 UTCEPSS rescore
  27. 2026-08-05 19:15 UTCEPSS rescore
  28. 2026-08-04 10:34 UTCEPSS rescore
  29. 2026-08-04 03:27 UTCOSV refresh
  30. 2026-08-03 10:33 UTCEPSS rescore
  31. 2026-08-02 02:24 UTCEPSS rescore
  32. 2026-08-01 04:13 UTCEPSS rescore
  33. 2026-07-30 16:25 UTCEPSS rescore
  34. 2026-07-30 01:28 UTCEPSS rescore
  35. 2026-07-28 15:33 UTCEPSS rescore
  36. 2026-07-26 14:52 UTCEPSS rescore
  37. 2026-07-26 14:52 UTCEPSS rescore
  38. 2026-07-25 14:15 UTCEPSS rescore
  39. 2026-07-24 14:15 UTCEPSS rescore
  40. 2026-07-23 14:16 UTCEPSS rescore
  41. 2026-07-23 02:09 UTCEG score recompute
  42. 2026-07-22 22:56 UTCEG score recompute
  43. 2026-07-22 14:06 UTCEPSS rescore
  44. 2026-07-22 14:06 UTCEPSS rescore
  45. 2026-07-21 15:22 UTCEPSS rescore
  46. 2026-07-21 15:22 UTCEPSS rescore
  47. 2026-07-20 17:05 UTCEPSS rescore
  48. 2026-07-19 14:29 UTCEPSS rescore
  49. 2026-07-19 02:27 UTCEPSS rescore
  50. 2026-07-18 10:02 UTCEPSS rescore
  51. 2026-07-18 10:02 UTCEPSS rescore
  52. 2026-07-17 22:29 UTCOSV refresh
  53. 2026-07-16 17:00 UTCEPSS rescore
  54. 2026-07-16 17:00 UTCEPSS rescore
  55. 2026-07-15 16:56 UTCEPSS rescore
  56. 2026-07-15 16:56 UTCEPSS rescore
  57. 2026-07-15 01:58 UTCEPSS rescore
  58. 2026-07-15 01:58 UTCEPSS rescore
  59. 2026-07-13 22:27 UTCEPSS rescore
  60. 2026-07-13 06:11 UTCEPSS rescore
  61. 2026-07-13 06:11 UTCEPSS rescore
  62. 2026-07-12 05:44 UTCEPSS rescore
  63. 2026-07-11 08:25 UTCEPSS rescore
  64. 2026-07-09 19:07 UTCEPSS rescore
  65. 2026-07-08 15:12 UTCEPSS rescore
  66. 2026-07-07 13:44 UTCEPSS rescore
  67. 2026-07-06 16:25 UTCEPSS rescore
  68. 2026-07-06 16:25 UTCEPSS rescore
  69. 2026-07-06 02:21 UTCEPSS rescore
  70. 2026-07-05 02:28 UTCEPSS rescore
  71. 2026-07-04 06:29 UTCEPSS rescore
  72. 2026-07-04 06:29 UTCEPSS rescore
  73. 2026-07-01 15:04 UTCEPSS rescore
  74. 2026-06-30 23:20 UTCEPSS rescore
  75. 2026-06-30 23:20 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-50915
    First seen May 11, 2022

    Anuko Time Tracker - SQLi (Authenticated)

    Open source ↗
  • GitHub PoCAltelus1/CVE-2022-24707
    First seen May 3, 2022

    PoC of CVE-2022-24707

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-24707?
CVE-2022-24707 is a high vulnerability published on February 24, 2022. Anuko Time Tracker is an open source, web-based time tracking application written in PHP. UNION SQL injection and time-based blind injection vulnerabilities existed in Time Tracker Puncher plugin in versions of anuko timetracker prior to 1.20.0.5642. This was happening because the Puncher plugin…
When was CVE-2022-24707 disclosed?
CVE-2022-24707 was first published on February 24, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-24707 actively exploited?
CVE-2022-24707 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.2% probability of exploitation in the next 30 days (94th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-24707?
CVE-2022-24707 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2022-24707?
A fix for CVE-2022-24707 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-24707

Explore →

Is Your Infrastructure Affected by CVE-2022-24707?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs