CVE-2026-12901
Deferred Deferred - Pending Action

Worldpay Payment Forgery in GetPaid WordPress Plugin

Vulnerability report for CVE-2026-12901, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-06

Last updated on: 2026-08-26

Assigner: WPScan

Description

The GetPaid WordPress plugin before 2.8.55 does not verify the authenticity of incoming Worldpay payment notifications, allowing unauthenticated attackers to forge a notification that marks a pending invoice as paid without any payment being made.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-06
Last Modified
2026-08-26
Generated
2026-08-27
AI Q&A
2026-08-07
EPSS Evaluated
2026-08-26
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
getpaid getpaid to 2.8.55 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-345 The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the GetPaid WordPress plugin before version 2.8.55. It allows unauthenticated attackers to forge payment notifications from Worldpay, tricking the system into marking invoices as paid without any actual payment being made.

Detection Guidance

To detect this vulnerability, check if your WordPress site uses the GetPaid plugin version before 2.8.55. Inspect the plugin files for missing authentication checks on Worldpay payment notifications. Look for forged payment confirmations in server logs or database entries marked as paid without valid transactions.

Impact Analysis

Attackers could exploit this to obtain products or services without paying by falsifying payment confirmations. This could lead to financial losses for merchants using the plugin.

Compliance Impact

This vulnerability could lead to unauthorized transactions being recorded as paid, potentially violating compliance requirements for data integrity and financial accuracy in standards like GDPR and HIPAA. Unverified payment notifications may result in incorrect financial records, which could affect audit trails and regulatory reporting.

Mitigation Strategies

Update the GetPaid WordPress plugin to version 2.8.55 or later to address the vulnerability. Disable the plugin temporarily if an update is not immediately available.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-12901. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart