# CVE-2026-77013: Icollect <= 1.0.0 - Unauthenticated User and Term Creation via Unrestricted Method Dispatch

> Unauthenticated attackers can create WordPress user accounts and taxonomy terms due to missing capability checks in the Icollect plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-45wp-4v6m-9hfj

## What is CVE-2026-77013?

CVE-2026-77013 is a medium-severity missing authorization vulnerability in Unknown 爱采集数据采集和发布插件, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 爱采集数据采集和发布插件 WordPress plugin through 1.0.0 does not restrict which of its handler methods a request may invoke, and performs no capability or nonce check on them, allowing unauthenticated users to create WordPress user accounts and taxonomy terms.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-77013?


## How do I fix CVE-2026-77013?

No fix has been published for CVE-2026-77013 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-77013 being exploited?

There is no known exploitation of CVE-2026-77013 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77013 and fix it if it is affected.

What it is: CVE-2026-77013 is a medium-severity missing authorization vulnerability in Unknown 爱采集数据采集和发布插件, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77013 in the wild and no public exploit code.

Affected product: Unknown 爱采集数据采集和发布插件. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77013/ (Markdown: https://insights.sbomify.com/CVE-2026-77013/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77013
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77013
- OSV: https://osv.dev/vulnerability/CVE-2026-77013

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77013/
Summaries are generated and may contain mistakes; the official description above is the record.