← Back
CVE-2026-49260
high
CVSS 8.2
OS Command Injection in pontedilana/php-weasyprint (CVE-2026-49260)
Summary
OS command injection in pontedilana/php-weasyprint (CVE-2026-49260). Successful exploitation can lead to full system takeover. Exploitable via ``master``. Mitigation: upgrade to `2.5.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-49260** has been found in pontedilana/php-weasyprint.
Attackers can target a specific entry point like ``master`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.2/10.
What to do: upgrade pontedilana/php-weasyprint to **2.5.1** or later.
If unsure, ask your IT team or search "pontedilana/php-weasyprint CVE-2026-49260" on the vendor's site.
CVE-2026-49260 (pontedilana/php-weasyprint) — CWE-78 / CVSS v3 8.2
Attack vector: local / no user interaction
Attack surface: `master` / `c2b51fed0bf442c3bf0292b879a09944d436f2a0` / `Pdf` / `buildCommand`
Patched: `2.5.1` — 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
**OS command injection** (CWE-78) exists in pontedilana/php-weasyprint. Attackers reach the vulnerable code path via ``master`` without authentication.
📍 Affected scope
pontedilana/php-weasyprint — . Attack surface: `master` / `c2b51fed0bf442c3bf0292b879a09944d436f2a0` / `Pdf` / `buildCommand`.
🔥 Severity
Severity: High (CVSS 8.2/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.5.1**.
🛡️ 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 'pontedilana/php-weasyprint' .` 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 'pontedilana/php-weasyprint' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pontedilana/php-weasyprint` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pontedilana/php-weasyprint to 2.5.1ステージング環境で 2.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
pontedilana/php-weasyprint
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.5.1"}]}]
References
- web https://github.com/KnpLabs/snappy/security/advisories/GHSA-vpr4-p6fq-85jc
- web https://github.com/pontedilana/php-weasyprint/commit/9e86a2b317237fc5728f712f5037164530117f7e
- web https://github.com/pontedilana/php-weasyprint/releases/tag/2.5.1
- web https://github.com/pontedilana/php-weasyprint/security/advisories/GHSA-f5gc-qxf8-mh9g
- web https://nvd.nist.gov/vuln/detail/CVE-2026-49260
- web https://github.com/advisories/GHSA-f5gc-qxf8-mh9g