Approved changes feed: RSS · Atom
cpe:2.3:a:kamleshyadav:handily:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Kamleshyadav (9468a0d3-8e29-564a-9a34-55dcb44bf399) |
|---|---|
| Product | Handily (af991e21-e755-5bb0-96eb-d27c9a5b765e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-14487 |
vulnerable | 2026-10-13 12:22:58.576314 |
Handily <= 1.0.3 - Missing Authorization to Unauthenticated Arbitrary Stripe Payment Settings Modification via 'stripe_publishbale_key' Parameter
MEDIUM (5.3)
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.
Published: 2026-09-22T07:41:14.339Z
Updated: 2026-09-22T10:25:31.838Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.