CVE-2023-51711: An issue was discovered in Regify Regipay Client for Windows version 4.5.1.0 allows DLL hijacking: a user can
CVE-2023-51711 is a high-severity flaw (CVSS 7.8) affecting regipay. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
An issue was discovered in Regify Regipay Client for Windows version 4.5.1.0 allows DLL hijacking: a user can trigger the execution of arbitrary code every time the product is executed.
Why this priority
- High severity
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.8 (High) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.2% (top 90%) |
| CISA exploited list | No |
| Weakness | CWE-427 |
| Published | 2024-01-24 |
| Last modified | 2026-06-17 |
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-51711?
regipay: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2023-51711 being exploited?
CVE-2023-51711 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-51711 affect?
CVE-2023-51711 affects regipay. Severity is high (CVSS 7.8). An issue was discovered in Regify Regipay Client for Windows version 4.5.1.0 allows DLL hijacking: a user can trigger the execution of arbitrary code every time the product is executed.
How urgent is CVE-2023-51711?
Priority 30/100. High severity