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.
CVE-2026-77012
Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-29. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.3
- EG Score
- 9.3(high)
- EG Risk
- 57(Track)EG Risk 57/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity93% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
August 29, 2026
Last Modified
August 30, 2026
Advisory Details (1)
Auto-updated Aug 30, 2026Icollect <= 1.0.0 – Unauthenticated Arbitrary File Read, SSRF and Path Traversal File Write via Default Publishing Password | CVE 2026-77012 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/025664f8-2af7-4692-a9a0-1d28916a1565/Vendor Advisories for CVE-2026-77012(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 05:45 UTCEG score recompute
- 2026-08-30 05:45 UTCGHSA enrichment
- 2026-08-30 01:29 UTCEG score recompute
- 2026-08-30 01:29 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-30 01:09 UTCEG score recompute▲ 9.30
- 2026-08-30 01:08 UTCGHSA enrichment
- 2026-08-30 01:08 UTCMITRE cvelistV5CVSS v3 → 9.3 · severity → CRITICAL
- 2026-08-29 06:21 UTCNVD update
- 2026-08-29 06:13 UTCEG score recompute
- 2026-08-29 06:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p91CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-77012?
When was CVE-2026-77012 disclosed?
Is CVE-2026-77012 actively exploited?
What is the CVSS score of CVE-2026-77012?
How do I remediate CVE-2026-77012?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77012
Is Your Infrastructure Affected by CVE-2026-77012?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.