Unauthenticated session takeover via reflected OCSESSID
Published May 10, 2026 · Updated May 10, 2026
Session fixation in OpenCart 3.0.3.8 allows remote attackers to hijack user sessions by supplying a chosen OCSESSID cookie. OpenCart's session-cookie processing accepts the attacker-selected value and returns the same identifier in Set-Cookie instead of generating a fresh value. The published record requires no prior privileges or user interaction; successful fixation enables unauthorized account access.
Summary
What happened
Session fixation in OpenCart 3.0.3.8 allows remote attackers to hijack user sessions by supplying a chosen OCSESSID cookie. OpenCart's session-cookie processing accepts the attacker-selected value and returns the same identifier in Set-Cookie instead of generating a fresh value. The published record requires no prior privileges or user interaction; successful fixation enables unauthorized account access.
The record
- CVE
- CVE-2021-47923
- Published
- May 10, 2026
- Updated
- May 10, 2026
- Vendor
- OpenCart
- Product
- OpenCart
- Classifications
- CWE-290, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 10, 2026CVE publishedPublication date reported by the CVE source.
- May 10, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.3.8
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- OpenCart 3.0.3.8 session-injection proof of conceptproof of concept · demonstrated
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