CVE-2026-94261

Sifalo Pay 2.0 - 2.5.2 - Unauthenticated Payment Confirmation Forgery via an Unbound Transaction Id

  • Medium 5.3
  • A public exploit reference is listed

Description

The Sifalo Pay WordPress plugin before 2.5.3 does not verify that a payment transaction identifier belongs to the order it is confirming, nor that the requester owns that order, allowing unauthenticated attackers holding one valid transaction identifier from a payment of their own to mark arbitrary pending orders as paid.

Key facts

Published
14 Oct 2026
Last changed
14 Oct 2026
Assigned by
WPScan
EPSS
0.239% likely to be exploited in the next 30 days, higher than 15.097% of CVEs (scores for 18 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.3CVSS 3.1, Mediumfrom CISA (ADP container)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
UnknownSifalo Pay
  • Default status: unaffected
  • 2.0 up to but excluding 2.5.3 (affected)

Timeline

  1. 14 Oct 2026 Published

Weakness

References