Vulnerability in solidtime (CVE-2026-42279)
Summary
Vulnerability in solidtime (CVE-2026-42279). Data can be tampered with by attackers. Exploitable via PUT /api/v1/organizations/{organization}/time-entries/{timeEntry}.
Original description
The description as published by the source.
solidtime is an open-source time-tracking app. In version 0.12.0, the PUT /api/v1/organizations/{organization}/time-entries/{timeEntry} API accepts a route-bound timeEntry from another organization when the caller has time-entries:update:all in the URL organization, allowing a known foreign time-entry UUID to be modified and rebound to objects in the caller's organization. This issue has been patched in version 0.12.1.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42279 has been found in solidtime.
Attackers can target a specific entry point like PUT /api/v1/organizations/{organization}/time-entries/{timeEntry} over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "solidtime CVE-2026-42279" on the vendor's site.
CVE-2026-42279 (solidtime) — CWE-639 / CVSS v3 5.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PUT /api/v1/organizations/{organization}/time-entries/{timeEntry}
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in solidtime. Attackers reach the vulnerable code path via PUT /api/v1/organizations/{organization}/time-entries/{timeEntry}.
Check the vendor advisory for the affected versions of solidtime. Attack surface: PUT /api/v1/organizations/{organization}/time-entries/{timeEntry}.
Severity: Medium (CVSS 5.8/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PUT /api/v1/organizations/{organization}/time-entries/{timeEntry} requests with malformed payloads or SQL meta-characters. Run grep -r 'solidtime' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'solidtime' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
solidtimeを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'PUT /api/v1/organizations/{organization}/time-entries/{timeEntry}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /api/v1/organizations/{organization}/time-entries/{timeEntry}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PUT /api/v1/organizations/{organization}/time-entries/{timeEntry} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- web github.com