CVE-2022-30357 is a high severity account takeover flaw in OvalEdge 5.2.8.0 and earlier, scored 8.8. A logged-in user can change the email address of a privileged account through the profile update function and then use password reset. I found no fixed version, so ask OvalEdge for one.
What's affected
The record says OvalEdge 5.2.8.0 and earlier is affected. The only source in the record is the researcher's disclosure page. It describes the issue as an account takeover through a POST request to the profile update function, using a user identifier and an email parameter, with authentication required.
The researcher's page explains the follow-on step: once a privileged user's email address is changed to one the attacker controls, the attacker uses the forgot password feature, assuming SMTP is configured, to reset the password. I am leaving out request details, because the weakness is described well enough without them.
I could not find a vendor advisory or a fixed version in the sources. Do not assume that a later 5.x build fixes this without confirmation from OvalEdge.
NVD scores the flaw 8.8 High with a network vector, low privileges and high impact across confidentiality, integrity and availability. The weakness class is cross-site request forgery (CWE-352), which does not quite match the researcher's description of a missing authorization check. The record's kev flag is false.
Weakness class per the record: CWE-352.
How to check if you're exposed
Find your OvalEdge version in the application's About or admin settings and compare it with 5.2.8.0. If you run that version or an earlier one, treat the flaw as present until OvalEdge confirms a fix.
Then look for evidence of misuse. Review audit logs for email address changes on administrator and other privileged accounts, and for password reset emails sent to unexpected addresses. Check your mail system's logs for reset messages tied to privileged users.
Also check how many people have accounts. The attack needs only a normal authenticated user, so a broad user base raises the risk.
What to do now
- Confirm the OvalEdge version in use and contact the vendor for a fixed release.
- Review audit logs for unexpected profile or email changes on privileged accounts, and reset those accounts if anything looks off.
- Limit access to the application to people who need it and require single sign-on if available.
- Add monitoring for email address changes on administrator accounts.
Why it matters
Account takeover through a profile change is a familiar design failure. The server accepted a request to change another user's email without checking that the caller was allowed to change that user. Combined with a password reset that trusts the email address on file, a low privileged account becomes a path to an administrator.
The two features are individually normal. The danger is in their combination, which is why changes to the recovery email address deserve the same protection as changes to a password, such as asking for the current password or sending a notification to the old address.
Data catalog tools often hold broad metadata and connection details for many systems, so a takeover of their administrator account has wide consequences.
Quick check
Is a fixed version known?
Not from the sources I could read. The record points only to the researcher's page, so ask OvalEdge directly.
Sources
Last reviewed: 19 October 2026.