Unauthenticated code execution via payment validation command injection
Published Oct 31, 2023 · Updated Sep 17, 2024
OS command injection in the Franfinance module before 2.0.27 allows remote attackers to execute arbitrary code during payment validation. The payment-validation handlers send Atos SIPS v1 response data to a decryption binary through PHP exec(), allowing an injected executable script to enter that sequence. Versions before 1.9.0 on PrestaShop 1.6 are reachable even when disabled; versions before 2.0.27 on PrestaShop 1.7 require the module to be enabled.
Summary
What happened
OS command injection in the Franfinance module before 2.0.27 allows remote attackers to execute arbitrary code during payment validation. The payment-validation handlers send Atos SIPS v1 response data to a decryption binary through PHP exec(), allowing an injected executable script to enter that sequence. Versions before 1.9.0 on PrestaShop 1.6 are reachable even when disabled; versions before 2.0.27 on PrestaShop 1.7 require the module to be enabled.
The record
- CVE
- CVE-2023-43139
- Published
- Oct 31, 2023
- Updated
- Sep 17, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-78, T1059, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 31, 2023CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo