Skip to main content

爱采集 (WordPress plugin) EUVDEUVD-2026-68057

| CVE-2026-77012 CRITICAL
Server-Side Request Forgery (SSRF) (CWE-918)
2026-08-29 WPScan GHSA-62hm-x77c-87qw
9.3
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Locate site running vulnerable plugin
  2. Delivery
    Send request with hardcoded secret
  3. Exploit
    Bypass endpoint authorization
  4. Execution
    Read config / trigger SSRF
  5. Persist
    Write PHP shell outside uploads
  6. Impact
    Execute code as web user

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires only that the 爱采集数据采集和发布插件 plugin (version ≤ 1.0.0) be installed and active, with its vulnerable unauthenticated endpoint network-reachable; the attacker must supply the plugin's hardcoded default secret, which is identical and publicly discoverable across all installs, so it is not a real barrier. No WordPress account, user interaction, or non-default configuration is needed (CVSS PR:N/UI:N). The primary limiting factor is deployment: the flaw is only exploitable where this specific, niche plugin is present, and file-write-to-RCE outcomes depend on the web server user's filesystem permissions and PHP execution in the writable location.

Impact

The signals are mixed but lean toward genuine priority for anyone actually running this plugin. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N, base 9.3) reflects a network-reachable, low-complexity, unauthenticated flaw with a scope change - consistent with the description of an unauthenticated endpoint gated only by a shared hardcoded secret. Publicly available exploit code raises operational risk, and the combination of arbitrary file write outside uploads plus SSRF realistically escalates beyond the modeled I:L toward remote code execution. Counterbalancing this, EPSS is only 0.14% (3rd percentile) and there is no CISA KEV listing, so it is not confirmed actively exploited; the low EPSS most likely reflects the plugin's tiny deployment footprint rather than low exploitability. Any operator who has this specific plugin installed should treat it as urgent given the trivial, unauthenticated, pre-patched attack path, while the broader ecosystem risk is limited by how rarely the plugin is deployed.

Exploit ScenarioDerived

An unauthenticated attacker sends a crafted HTTP request to the plugin's exposed endpoint, supplying the known hardcoded default secret and a target URL or path parameter. They first read wp-config.php to harvest database credentials and salts, then use the SSRF to probe internal services or cloud metadata, and finally write a PHP web shell outside the uploads directory to achieve code execution. Public exploit code for this issue exists, lowering the skill required.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAI

Unauthenticated file read, SSRF, and arbitrary file write affect the 爱采集数据采集和发布插件 (an auto-collection/scraping-and-publishing) WordPress plugin through version 1.0.0, because one of its unauthenticated endpoints trusts a hardcoded default secret instead of a per-install value and fails to validate supplied URLs and destination paths. Remote attackers with no authentication can read arbitrary server files, coerce the server into issuing arbitrary outbound requests and returning the responses, and write attacker-controlled content outside the uploads directory. Publicly available exploit code exists (reported by WPScan), though EPSS remains low at 0.14% (3rd percentile).

RemediationAI

No fixed version is identified in the provided data - the plugin is described only as vulnerable 'through 1.0.0' with no vendor-released patch confirmed at time of analysis, so treat this as No vendor-released patch identified at time of analysis and verify the latest status via the WPScan advisory (https://wpscan.com/vulnerability/025664f8-2af7-4692-a9a0-1d28916a1565/). Given the unauthenticated exploitation and public exploit, the safest compensating control is to deactivate and uninstall the plugin until a fixed release is confirmed (side effect: the auto-collection/publishing functionality is lost). If it must remain active, block or restrict external access to the plugin's vulnerable AJAX/REST endpoint at the web server or WAF layer and deny outbound requests from the web server to internal ranges and cloud metadata (e.g., 169.254.169.254) to blunt the SSRF (side effect: legitimate remote-fetch features may break); additionally enforce filesystem permissions so the web user cannot write outside the uploads directory or into PHP-executable paths. Because the shared secret is hardcoded, changing site-level configuration will not neutralize the auth bypass - removal or upstream code fix is required.

Affected VersionsENISA

爱采集数据采集和发布插件 0 ≤1.0.0

Affected Packages

euvd 爱采集数据采集和发布插件 no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is a WordPress plugin (PHP) that exposes an endpoint reachable without WordPress authentication. Two root-cause weaknesses combine: an authentication/authorization failure where a shared hardcoded default secret is accepted in place of a per-install secret (so the secret is identical and known across every deployment), and missing input validation on the URL and filesystem path parameters. CWE-918 (Server-Side Request Forgery) captures the SSRF primitive - the server can be made to fetch attacker-chosen URLs and disclose the responses, which is especially dangerous inside cloud/metadata or internal-network contexts. The same lack of path validation extends the impact to arbitrary file read (path traversal to sensitive files such as wp-config.php) and arbitrary file write outside the intended uploads directory, which can enable web-shell placement and code execution.

Know when WordPress gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 9.3 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
vuln.today AI 10.0 CRITICAL

Unauthenticated network endpoint gated only by a shared hardcoded secret (PR:N/AC:L); arbitrary out-of-directory file write justifies I:H, arbitrary read C:H, and SSRF crossing trust boundaries S:C.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

Lifecycle Timeline

3
CVE Published
Aug 31, 2026 - 10:50 cve.org
CRITICAL 9.3
CVSS changed
Aug 30, 2026 - 01:22 NVD
9.3 (CRITICAL)
CVE Published
Aug 29, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

Technical POC Analysis

The affected component is the WordPress plugin icollect through version 1.0.0.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Threat Intelligence Overview

EPSS Score
0.1%
Top 97% exploitable
Prevalence
Rare
obscure niche Chinese WordPress plugin, tiny install base
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
CRITICAL severity + public POC available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

66
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

CVE-2016-10033 CRITICAL POC
9.8 Dec 30

The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para

CVE-2016-10045 CRITICAL POC
9.8 Dec 30

The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2024-8353 CRITICAL POC
9.8 Sep 28

The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-11749 CRITICAL POC
9.8 Nov 05

The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2026-63030 CRITICAL POC
9.8 Jul 17

Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy