# CVE-2025-14487: Missing authorization in Handily

> Unauthenticated attackers can modify Stripe payment settings in the Handily WordPress plugin, potentially redirecting payments to their own accounts.

- **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:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-rqq6-mm6q-4qqx

## What is CVE-2025-14487?

CVE-2025-14487 is a medium-severity missing authorization vulnerability in kamleshyadav Handily, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Handily plugin for WordPress is vulnerable to unauthorized payment settings modification due to missing authorization checks in all versions up to, and including, 1.0.3. This makes it possible for unauthenticated attackers to modify Stripe payment configuration settings, including publishable keys, secret keys, email addresses, success URLs, and cancel URLs via the payment settings parameters. This could allow attackers to redirect payments to their own Stripe accounts.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-14487 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14487 is a medium-severity missing authorization vulnerability in kamleshyadav Handily, published on 22 Sep 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-2025-14487 in the wild and no public exploit code.

Affected product: kamleshyadav Handily. 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-14487/ (Markdown: https://insights.sbomify.com/CVE-2025-14487/index.md)
```

## Sources

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

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