CVE-2025-61924VulnerabilityPublished 16 Oct 2025

CVE-2025-61924: PrestaShopCorp ps_checkout · Incomplete List of Disallowed Inputs

Affects PrestaShopCorp ps_checkoutSource CVE Database V5

Not known to be exploited · CVSS 3.8 Low : upgrade to 4.4.1 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.8Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.4.1

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade prestashopcorp/ps_checkout to 4.4.1.

Affected software

Product	Affected	Fixed in
GitHubprestashopcorp/ps_checkout`pkg:github/prestashopcorp/ps_checkout`Other threats	Affected <4.4.1	Fixed in 4.4.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately verify their ps_checkout module version and upgrade to version 4.4.1 or 5.0.5 or later to remediate the vulnerability. Since no workarounds exist, patching is the only effective mitigation. Additionally, organizations should enforce strict access controls on backoffice accounts, including multi-factor authentication (MFA) for administrative users, to reduce the risk of credential compromise. Regular auditing and monitoring of backoffice activities can help detect unauthorized changes to payment configurations. Implementing role-based access control (RBAC) to limit the number of users with merchant account modification privileges is advisable. Organizations should also review logs for suspicious activity related to payment settings and consider isolating payment configuration functions to minimize exposure. Finally, educating staff about phishing and credential security can reduce the risk of initial compromise.

Description

PrestaShop Checkout is the PrestaShop official payment module in partnership with PayPal. In versions prior to 4.4.1 and 5.0.5, the Target PayPal merchant account hijacking from backoffice due to wrong usage of the PHP array_search(). The vulnerability is fixed in versions 4.4.1 and 5.0.5. No known workarounds exist.

Impact

For European organizations, especially e-commerce businesses using PrestaShop with the ps_checkout module, this vulnerability poses a risk of financial fraud through merchant account hijacking. An attacker with backoffice access could redirect payments or manipulate transaction data, leading to direct financial losses and reputational damage. Given the widespread use of PrestaShop in Europe, particularly among small and medium-sized enterprises (SMEs) in countries with strong e-commerce sectors like Germany, France, Spain, and Italy, the impact could be significant if exploited. The vulnerability does not affect availability, so operational disruption is unlikely, but the breach of payment integrity could lead to regulatory scrutiny under GDPR due to potential unauthorized access to payment-related personal data. The requirement for high privileges limits the threat to insiders or attackers who have already compromised administrative credentials, emphasizing the importance of strong access controls and monitoring.

CWE-184Incomplete List of Disallowed Inputs (opens in a new tab)
Base weaknessOWASP Top 10 A03:2021: Injection (opens in a new tab)
The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete.
Implementation · Input Validation
Do not rely exclusively on detecting disallowed inputs. There are too many variants to encode a character, especially when different environments are used, so there is a high likelihood of missing some variants. Only use detection of disallowed inputs as a mechanism for detecting suspicious activity.
Attack patterns
Double Encoding (opens in a new tab)
Command Delimiters (opens in a new tab)
Flash Injection (opens in a new tab)
Using Leading 'Ghost' Character Sequences to Bypass Input Filters (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/PrestaShopCorp/ps_checkout/security/advisories/GHSA-wvpg-4wrh-5889 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Oct 2025, 17:59 UTC

WeaknessesCWE-184

Technical details

References

Community reviews

Related threats