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.
Published: 2026-09-22
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized Payment Configuration Modification
Action: Apply Patch
AI Analysis

Impact

The Handily plugin contains a missing authorization check that allows any user, even those not logged in, to alter Stripe payment settings such as publishable keys, secret keys, and URL redirects. By changing these values an attacker can redirect customers’ payments to a Stripe account controlled by the attacker, resulting in loss of revenue and possible fraud. The vulnerability is a direct authorization flaw (CWE‑862). The plugin’s operational integrity is thus compromised.

Affected Systems

The vulnerability is present in all released versions of the Handily WordPress plugin up to and including 1.0.3, distributed by the vendor Kamleshyadav. Only users of these versions are affected; newer releases are presumed fixed.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity. No EPSS score is available, but the lack of a public exploit and the absence from CISA KEV suggest the attack probability is low to moderate. An attacker would need to send a request that includes the payment settings parameters to a public WordPress site running Handily. Without authentication, the request will be processed because the plugin does not check user privileges, allowing the attacker to immediately overwrite Stripe credentials.

Generated by OpenCVE AI on September 22, 2026 at 09:54 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Handily plugin to a version newer than 1.0.3 to apply the vendor’s fix.
  • Configure a web‑application firewall or server rule to block unauthenticated users from accessing any endpoint that accepts payment configuration parameters in Handily.
  • If an upgrade is not immediately possible, disable or remove the Handily plugin to eliminate the attack surface.

Generated by OpenCVE AI on September 22, 2026 at 09:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 22 Sep 2026 11:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 22 Sep 2026 08:00:00 +0000

Type Values Removed Values Added
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.
Title Handily <= 1.0.3 - Missing Authorization to Unauthenticated Arbitrary Stripe Payment Settings Modification via 'stripe_publishbale_key' Parameter
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-09-22T10:25:31.838Z

Reserved: 2025-12-10T20:25:21.634Z

Link: CVE-2025-14487

cve-icon Vulnrichment

Updated: 2026-09-22T10:16:52.646Z

cve-icon NVD

Status : Received

Published: 2026-09-22T08:16:35.987

Modified: 2026-09-22T11:17:23.103

Link: CVE-2025-14487

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-22T10:00:15Z

Weaknesses