Unauthorized payment settings changes via missing CSRF check
Published Oct 17, 2023 · Updated Sep 13, 2024
CSRF in Open Journal Systems before 3.3.0-16 allows remote authenticated users to alter payment types through a manager's browser. PaymentTypesForm accepts payment-type changes without applying FormValidatorCSRF to verify that the request originated from the legitimate form. A low-privileged remote user must induce an authenticated manager to submit the forged request; the resulting change is limited to payment configuration.
Summary
What happened
CSRF in Open Journal Systems before 3.3.0-16 allows remote authenticated users to alter payment types through a manager's browser. PaymentTypesForm accepts payment-type changes without applying FormValidatorCSRF to verify that the request originated from the legitimate form. A low-privileged remote user must induce an authenticated manager to submit the forged request; the resulting change is limited to payment configuration.
The record
- CVE
- CVE-2023-5626
- Published
- Oct 17, 2023
- Updated
- Sep 13, 2024
- Vendor
- Public Knowledge Project
- Product
- Open Journal Systems
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 17, 2023CVE publishedPublication date reported by the CVE source.
- Sep 13, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.3.0-16
- Affected versionversion=unspecified <3.3.0-16
What conditions does exploitation require?
What is affected?
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