SSRF (Server-Side Request Forgery) in 爱采集数据采集和发布插件 (WordPress plugin) (CVE-2026-77012)
Summary
SSRF in 爱采集数据采集和发布插件 (WordPress plugin) (CVE-2026-77012). Confidential information can be exposed externally.
Original description
The description as published by the source.
The 爱采集数据采集和发布插件 WordPress plugin through 1.0.0 does not require a per-install secret for one of its unauthenticated endpoints, relying on a hardcoded default, and does not validate the URLs or destination paths it is given, allowing unauthenticated attackers to read arbitrary files from the server, force it to issue arbitrary requests and retrieve the responses, and write attacker-supplied content outside the uploads directory.
Source: GitHub Security Advisories (Global) 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-77012 has been found in 爱采集数据采集和发布插件 (WordPress plugin).
Confidential information can be exposed externally. CVSS score: 9.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "爱采集数据采集和发布插件 (WordPress plugin) CVE-2026-77012" on the vendor's site.
CVE-2026-77012 (爱采集数据采集和发布插件 (WordPress plugin)) — CWE-918 / CVSS v3 9.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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.
SSRF (CWE-918) exists in 爱采集数据采集和发布插件 (WordPress plugin).
Check the vendor advisory for the affected versions of 爱采集数据采集和发布插件 (WordPress plugin).
Severity: Critical (CVSS 9.3/10). Confidential information can be exposed externally.
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 request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで 爱采集数据采集和发布插件 (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web wpscan.com
- web github.com
- web contact@wpscan.com