Authenticated code execution via htmlFile inclusion
Published Jan 18, 2023 · Updated Apr 4, 2025
Code injection in OpenText Content Server 16.2.2 through 22.3 allows remote authenticated users to execute OScript code. Multiple endpoints pass the htmlFile parameter into the HTML rendering pipeline, which evaluates embedded OScript rather than treating the referenced file only as content. A low-privilege account can reach the affected endpoints and run filesystem, network, or operating-system commands under the server process.
Summary
What happened
Code injection in OpenText Content Server 16.2.2 through 22.3 allows remote authenticated users to execute OScript code. Multiple endpoints pass the htmlFile parameter into the HTML rendering pipeline, which evaluates embedded OScript rather than treating the referenced file only as content. A low-privilege account can reach the affected endpoints and run filesystem, network, or operating-system commands under the server process.
The record
- CVE
- CVE-2022-45928
- Published
- Jan 18, 2023
- Updated
- Apr 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 18, 2023CVE publishedPublication date reported by the CVE source.
- Apr 4, 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.
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
- SEC Consult CVE-2022-45928 proof of conceptfunctional · 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