Vulnerability in PHPipam (CVE-2018-1000870)

Summary

Vulnerability in PHPipam (CVE-2018-1000870). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.4 or later.

Original description

The description as published by the source.

PHPipam version 1.3.2 and earlier contains a CWE-79 vulnerability in /app/admin/users/print-user.php that can result in Execute code in the victims browser. This attack appear to be exploitable via Attacker change theme parameter in user settings. Admin(Victim) views user in admin-panel and gets exploited.. This vulnerability appears to have been fixed in 1.4.

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

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-2018-1000870 has been found in PHPipam.
Risk of unauthorized operations or information disclosure.
What to do: upgrade PHPipam to 1.4 or later.
If unsure, ask your IT team or search "PHPipam CVE-2018-1000870" on the vendor's site.

CVE-2018-1000870 (PHPipam)
Attack vector: remote (network-reachable)
Patched: 1.4 — apply immediately
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

A vulnerability (unclassified) exists in PHPipam.

📍 Affected scope

Check the vendor advisory for the affected versions of PHPipam.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.4.

🛡️ 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 request patterns matching this CVE's known IOCs. Run grep -r 'PHPipam' . 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

1
Identify exposure identify
```
grep -r 'PHPipam' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で PHPipam を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade PHPipam to 1.4
```
ステージング環境で 1.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

patch github.com
patch github.com