CVE-2023-40809: OpenCRX version 5.2.0 is vulnerable to HTML injection via the Activity Search Criteria-Activity Number.
CVE-2023-40809 is a medium-severity flaw (CVSS 6.1) affecting opencrx. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
OpenCRX version 5.2.0 is vulnerable to HTML injection via the Activity Search Criteria-Activity Number.
Why this priority
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2023-40809?
opencrx: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2023-40809 being exploited?
CVE-2023-40809 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2023-40809 affect?
CVE-2023-40809 affects opencrx. Severity is medium (CVSS 6.1). OpenCRX version 5.2.0 is vulnerable to HTML injection via the Activity Search Criteria-Activity Number.
How urgent is CVE-2023-40809?
Priority 36/100. Public exploit reference
Related CVEs
- CVE-2023-46502 CRITICAL 9.8 DOWNGRADE An issue in openCRX v.5.2.2 allows a remote attacker to read internal files and execute server side request fo
- CVE-2023-40817 MEDIUM 6.1 DOWNGRADE OpenCRX version 5.2.0 is vulnerable to HTML injection via the Product Configuration Name Field.
- CVE-2023-40816 MEDIUM 6.1 DOWNGRADE OpenCRX version 5.2.0 is vulnerable to HTML injection via Activity Milestone Name Field.
- CVE-2023-40815 MEDIUM 6.1 DOWNGRADE OpenCRX version 5.2.0 is vulnerable to HTML injection via the Category Creation Name Field.
- CVE-2023-40814 MEDIUM 6.1 DOWNGRADE OpenCRX version 5.2.0 is vulnerable to HTML injection via the Accounts Name Field.