← Back
GHSA-qv4m-m73m-8hj7
Path Traversal in notrinos/notrinos-erp (GHSA-qv4m-m73m-8hj7)
Summary
path traversal in notrinos/notrinos-erp (GHSA-qv4m-m73m-8hj7). Successful exploitation can lead to full system takeover. Exploitable via `POST /hrm/manage/employees.php`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-qv4m-m73m-8hj7** has been found in notrinos/notrinos-erp.
Attackers can target a specific entry point like `POST /hrm/manage/employees.php` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "notrinos/notrinos-erp GHSA-qv4m-m73m-8hj7" on the vendor's site.
GHSA-qv4m-m73m-8hj7 (notrinos/notrinos-erp) — CWE-22 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /hrm/manage/employees.php / GET /company/0/documents/employees/1_ / `SA_EMPLOYEE` / `pic`
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.
❓ What is the problem
**Path traversal** (CWE-22) exists in notrinos/notrinos-erp. Attackers reach the vulnerable code path via `POST /hrm/manage/employees.php` without authentication.
📍 Affected scope
notrinos/notrinos-erp — . Attack surface: POST /hrm/manage/employees.php / GET /company/0/documents/employees/1_ / `SA_EMPLOYEE` / `pic`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /hrm/manage/employees.php` requests with malformed payloads or SQL meta-characters. Run `grep -r 'notrinos/notrinos-erp' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'notrinos/notrinos-erp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `notrinos/notrinos-erp` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /hrm/manage/employees.php' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /hrm/manage/employees.php` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against POST /hrm/manage/employees.php on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
notrinos/notrinos-erp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Packagist
notrinos/notrinos-erp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.0.0"}]}]