Vulnerability in wordpress (DEBIAN-CVE-2017-8295)
Summary
Vulnerability in wordpress (DEBIAN-CVE-2017-8295). Data can be tampered with by attackers. Exploitable via Host header. Mitigation: upgrade to 4.7.5+dfsg-2 or later.
Original description
The description as published by the source.
WordPress through 4.7.4 relies on the Host HTTP header for a password-reset e-mail message, which makes it easier for remote attackers to reset arbitrary passwords by making a crafted wp-login.php?action=lostpassword request and then arranging for this message to bounce or be resent, leading to transmission of the reset key to a mailbox on an attacker-controlled SMTP server. This is related to problematic use of the SERVER_NAME variable in wp-includes/pluggable.php in conjunction with the PHP mail function. Exploitation is not achievable in all cases because it requires at least one of the following: (1) the attacker can prevent the victim from receiving any e-mail messages for an extended period of time (such as 5 days), (2) the victim's e-mail system sends an autoresponse containing the original message, or (3) the victim manually composes a reply containing the original message.
Source: OSV.dev (Open Source Vulnerabilities) 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 DEBIAN-CVE-2017-8295 has been found in wordpress.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade wordpress to 4.7.5+dfsg-2 or later.
If unsure, ask your IT team or search "wordpress DEBIAN-CVE-2017-8295" on the vendor's site.
DEBIAN-CVE-2017-8295 (wordpress)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Host header
Patched: 4.7.5+dfsg-2 — 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.
A vulnerability (unclassified) exists in wordpress. Attackers reach the vulnerable code path via Host header without authentication.
Check the vendor advisory for the affected versions of wordpress. Attack surface: Host header.
Severity: ?. Data can be tampered with by attackers.
Update to 4.7.5+dfsg-2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wordpress' . 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 'wordpress' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
wordpressを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade wordpress to 4.7.5+dfsg-2ステージング環境で 4.7.5+dfsg-2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory security-tracker.debian.org