External risk intelligence

爱采集 WordPress Plugin Arbitrary File Read and Request Forgery

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-77012

The vulnerability exists in a WordPress plugin, which is typically installed on public-facing web servers. Because the affected endpoints are unauthenticated and intended for data collection, they are commonly exposed to the internet as part of the standard deployment of such web applications.

Server-Side Request Forgery

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability in a WordPress plugin that handles data collection. The flaw allows unauthenticated attackers to potentially read sensitive files, execute arbitrary requests, and write malicious content to the server. The main concern is confirming relevance and exposure.

  • Plugin allows reading, writing, and requesting data.
  • Unauthenticated access to critical server functions.
  • Verify plugin use and potential external access.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted requests to an unauthenticated endpoint of the 爱采集数据采集和发布插件. Because the plugin does not properly validate URLs or destination paths and relies on a hardcoded default secret, an attacker could trick it into reading sensitive files from the server, sending arbitrary web requests, or writing malicious content to unintended locations. This could lead to information disclosure, denial of service, or further system compromise.

  • No authentication required.
  • Sends requests to vulnerable endpoint.
  • Risk of data exposure and code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to read arbitrary files from the server, issue arbitrary requests, and write content outside the designated uploads directory. These actions are possible when the affected WordPress plugin is installed and configured with its default, hardcoded secret, and when the plugin's endpoints are accessible.

  • Server files and data are at risk.
  • Unauthenticated requests can read files.
  • Arbitrary file writes and data retrieval.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world remediation efforts for this vulnerability will likely involve application owners and platform teams responsible for WordPress deployments. The first practical step is to identify all instances of the affected plugin, assess their exposure and criticality, and then coordinate with the responsible teams to plan remediation.

  • Application owners and platform teams.
  • Verify plugin installations and reachability.
  • Plan and execute remediation actions.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the 爱采集数据采集和发布插件?

This is a WordPress plugin designed to automate data collection and content publishing tasks. Users typically install it to streamline content management workflows, allowing the site to fetch external data and post it automatically. Because its primary function involves external communication and file handling, it interacts closely with both the server filesystem and the network.

How does CVE-2026-77012 affect the plugin?

This vulnerability is classified as Server-Side Request Forgery (CWE-918). It occurs because the plugin uses a hardcoded secret for its endpoints instead of requiring a unique, per-install password. By exploiting this, an attacker can bypass authentication to trick the server into interacting with internal files or sending unauthorized web requests on their behalf.

Do I need to be authenticated to trigger this flaw?

No. The vulnerability exists within unauthenticated endpoints, meaning anyone with network access to your site can send the malicious requests. The flaw is triggered by these crafted requests when the plugin relies on its default, hardcoded secret. It is not triggered if the endpoint is not reachable or if the plugin is not installed.

Is my site at risk according to Halo Surface Signal?

Yes, Halo Surface Signal flags this as a 'Likely' risk. Because this plugin is designed for data collection, its vulnerable endpoints are typically exposed to the internet as part of a standard WordPress deployment. If your site is public-facing, it is effectively accessible to the threat, making it important to determine if the plugin is active in your environment.

What is the first step to address this issue?

Start by identifying all WordPress installations within your infrastructure that currently use this specific plugin. Once you have a list of affected instances, assess whether they are internet-facing or handling sensitive data. Coordinate with your web development or platform teams to plan for disabling the plugin or applying vendor-supplied updates as soon as they are available.

References