# CVE-2025-1562: Missing authorization in FunnelKit Automations – Email Marketing Automation and CRM for WordPress & WooCommerce

> Unauthenticated attackers can install arbitrary plugins due to missing authorization checks, potentially leading to site compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jun 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-rr4m-6xx9-f2wg

## What is CVE-2025-1562?

CVE-2025-1562 is a critical missing authorization vulnerability in amans2k FunnelKit Automations – Email Marketing Automation and CRM for WordPress & WooCommerce, published on 18 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Recover WooCommerce Cart Abandonment, Newsletter, Email Marketing, Marketing Automation By FunnelKit plugin for WordPress is vulnerable to unauthorized arbitrary plugin installation due to a missing capability check on the install_or_activate_addon_plugins() function and a weak nonce hash in all versions up to, and including, 3.5.3. This makes it possible for unauthenticated attackers to install arbitrary plugins on the site that can be leveraged to further infect a vulnerable site.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-1562?

It affects 1 product.


Products: Funnelkit Funnelkit Automations.

## How do I fix CVE-2025-1562?

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

## Is CVE-2025-1562 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1562 exists.

Public exploit code:

- https://github.com/gmh5225/CVE-2025-1562 (github_poc): https://github.com/gmh5225/CVE-2025-1562
- Recover WooCommerce Cart Abandonment, Newsletter, Email Marketing, Marketing Automation By FunnelKit - Broken Access Control (nuclei): http/cves/2025/CVE-2025-1562.yaml

## Other vulnerabilities in amans2k FunnelKit Automations – Email Marketing Automation and CRM for WordPress & WooCommerce

- [CVE-2024-9186](https://insights.sbomify.com/CVE-2024-9186/): Automation By Autonami < 3.3.0 - Unauthenticated SQLi (high 8.6)
- [CVE-2024-47328](https://insights.sbomify.com/CVE-2024-47328/): SQL injection in FunnelKit Automations (high 7.6)
- [CVE-2023-50857](https://insights.sbomify.com/CVE-2023-50857/): WordPress Automation By Autonami Plugin <= 2.6.1 is vulnerable to SQL Injection (high 7.6)
- [CVE-2025-12468](https://insights.sbomify.com/CVE-2025-12468/): Information disclosure in FunnelKit Automations – Email Marketing Automation and CRM for WordPress & WooCommerce (medium 5.3)
- [CVE-2025-12469](https://insights.sbomify.com/CVE-2025-12469/): Missing authorization in FunnelKit Automations – Email Marketing Automation and CRM for WordPress & WooCommerce (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1562 and fix it if it is affected.

What it is: CVE-2025-1562 is a critical missing authorization vulnerability in amans2k FunnelKit Automations – Email Marketing Automation and CRM for WordPress & WooCommerce, published on 18 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1562 exists.

Affected product: amans2k FunnelKit Automations – Email Marketing Automation and CRM for WordPress & WooCommerce. 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-2025-1562/ (Markdown: https://insights.sbomify.com/CVE-2025-1562/index.md)
```

## Sources

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

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