Description
The Sifalo Pay WordPress plugin before 2.5.3 does not verify ownership of, or authorisation for, the order being updated when it handles a payment return, allowing unauthenticated attackers to write arbitrary payment session metadata onto any order in the store and to force any order awaiting payment into a failed state.
Published: 2026-10-14
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized Order Tampering
Action: Patch Now
AI Analysis

Impact

The Sifalo Pay WordPress plugin before version 2.5.3 lacks an ownership or authorization check during the payment return process, allowing an unauthenticated attacker to modify the payment session metadata of any order. This flaw permits the attacker to alter arbitrary fields associated with the payment session and to force an order that is awaiting payment into a failed state. The impacted data integrity and order state may be compromised. The vulnerability is classified as a permission‑check bypass (CWE‑862).

Affected Systems

Affected systems are WordPress installations that use the Sifalo Pay plugin in any version prior to 2.5.3, specifically from 2.0.0 through 2.5.2 inclusive. Sites that have not upgraded the plugin are vulnerable. The plugin handles payment processing and order updates for e‑commerce sites.

Risk and Exploitability

The flaw carries a CVSS score of 5.3, indicating moderate risk, and an EPSS score of less than 1%, suggesting a very low probability of exploitation in the wild. It is not listed in the CISA KEV catalog. The attack vector is external: an unauthenticated HTTP request to the payment return endpoint can trigger the vulnerability. An attacker must know or guess a valid order identifier to achieve an impact, but no privileged credentials are required.

Generated by OpenCVE AI on October 16, 2026 at 00:25 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Sifalo Pay WordPress plugin to version 2.5.3 or any later release that includes the authorization check.
  • Limit the payment return endpoint so that only authenticated requests originating from the payment gateway can reach it, and add explicit ownership verification before applying any changes to an order.
  • Audit existing orders for unauthorized modifications of payment session metadata, reset any altered fields, and restore orders that have been incorrectly forced to a failed state back to the correct status.

Generated by OpenCVE AI on October 16, 2026 at 00:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 14 Oct 2026 14:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-862
Metrics cvssV3_1

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


Wed, 14 Oct 2026 06:45:00 +0000

Type Values Removed Values Added
Description The Sifalo Pay WordPress plugin before 2.5.3 does not verify ownership of, or authorisation for, the order being updated when it handles a payment return, allowing unauthenticated attackers to write arbitrary payment session metadata onto any order in the store and to force any order awaiting payment into a failed state.
Title Sifalo Pay 2.0 - 2.5.2 - Unauthenticated Order Payment Metadata Modification and Forced Order Failure
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-10-14T13:42:20.700Z

Reserved: 2026-09-21T09:02:56.713Z

Link: CVE-2026-94260

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-10-14T07:17:05.370

Modified: 2026-10-14T16:14:02.800

Link: CVE-2026-94260

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-16T00:30:14Z

Weaknesses