Authenticated code execution via _oups parameter
Published Dec 13, 2022 · Updated Apr 22, 2025
Remote code execution in SPIP 3.1.13 through 4.1.2 allows remote authenticated users to execute arbitrary code via the _oups parameter. The vulnerable request handling passes attacker-controlled _oups input into PHP code-generation processing instead of safely constraining it. A remote user with valid SPIP authentication can reach the affected endpoint without additional interaction, obtaining code execution with the web application's privileges and associated confidentiality, integrity, and availability impact.
Summary
What happened
Remote code execution in SPIP 3.1.13 through 4.1.2 allows remote authenticated users to execute arbitrary code via the _oups parameter. The vulnerable request handling passes attacker-controlled _oups input into PHP code-generation processing instead of safely constraining it. A remote user with valid SPIP authentication can reach the affected endpoint without additional interaction, obtaining code execution with the web application's privileges and associated confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2022-37155
- Published
- Dec 13, 2022
- Updated
- Apr 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 13, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record 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
- SPIP 4.1.2 authenticated RCE write-upproof of concept · unverified
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