CVE-2026-77012: Icollect <= 1.0.0 - Unauthenticated Arbitrary File Read, SSRF and Path Traversal File Write via Default Publishing Password
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.
Security readout for executives and security teams
Plain-English summary
A WordPress plugin used for data collection and publishing reportedly exposes an unauthenticated endpoint protected only by a hardcoded default password. An internet attacker could read sensitive server files, make the site contact other systems, capture responses, or write content outside the intended uploads directory.
Executive priority
Treat confirmed internet-accessible installations as an immediate remediation and investigation priority. The vulnerability requires no privileges or user interaction and can expose secrets or alter files. If the plugin is unnecessary, disable it promptly; otherwise isolate its publishing functionality while seeking verified vendor guidance.
Technical view
爱采集数据采集和发布插件 through version 1.0.0 reportedly combines default-secret authentication with missing URL and destination-path validation. The resulting flaws enable arbitrary file read, server-side request forgery, and path-traversal file write without credentials or user interaction. The published CVSS 3.1 score is 9.3, with high confidentiality and low integrity impact.
Likely exposure
WordPress sites running the affected plugin through version 1.0.0 may be exposed if the vulnerable endpoint is internet-accessible. The supplied sources do not identify exact endpoint paths, configuration prerequisites, installation prevalence, or whether changing the publishing password fully prevents exploitation.
Exploitation context
CISA KEV inclusion is not reported, and the supplied material does not establish active exploitation. WPScan labels its reference as containing exploit information, indicating technical feasibility, but that alone is not evidence of attacks in the wild. No exploit details should be required for defensive prioritization.
Researcher notes
The record attributes SSRF to CWE-918, while the description also alleges arbitrary file read and path-traversal file write. Published scoring is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N. The bundle lacks endpoint identifiers, request conditions, patch information, and forensic indicators, so validation must remain configuration- and log-driven.
Mitigation direction
Inventory WordPress sites and identify installations of the affected plugin through version 1.0.0.
Disable or remove the plugin where operationally feasible until authoritative vendor guidance is available.
Check vendor and WPScan guidance for a patched version or documented mitigation.
Restrict public access to unnecessary plugin publishing functionality using existing access controls.
Rotate exposed credentials and secrets if investigation indicates sensitive files may have been read.
Validation and detection
Confirm the installed plugin version and whether its publishing endpoint is reachable without authentication.
Review web logs for unusual unauthenticated requests targeting the plugin's publishing functionality.
Review outbound connection logs for unexpected requests originating from affected WordPress servers.
Inspect files outside the uploads directory for unexplained additions or modifications.
Assess whether configuration files, credentials, keys, or other sensitive server files were exposed.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.