Safeguard
Vulnerability Analysis•

CVE-2022-30358: High Account Takeover in OvalEdge via Password Update

CVE-2022-30358 lets an authenticated OvalEdge 5.2.8.0 user change another user's password through the password update function. Ask OvalEdge for a fix.

Safeguard Security Team
3 min read

CVE-2022-30358 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 password of another account, including a privileged one, through the password update function. 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. Its only source is the researcher's disclosure page, which describes the flaw as an authenticated account takeover through a POST request to the password update function using a user identifier and a new password parameter.

The page gives the scenario in a heading: changing the password of a local privileged user. In plain terms, the server does not check that the caller is allowed to change the password of the account named in the request. I am leaving out the request itself.

No vendor advisory or fixed version appears in the record or the page I read, so I cannot say which release addresses the issue. Ask OvalEdge, and do not infer a fix from a version number.

NVD scores the flaw 8.8 High, with network vector and low privileges. The weakness class in the record is incorrect authorization (CWE-863), which matches the description better than the class on the sibling CVE-2022-30357. The kev flag is false.

Weakness class per the record: CWE-863.

How to check if you're exposed

Confirm the OvalEdge version from the application's About page or admin console. If it is 5.2.8.0 or earlier, assume it is affected.

Review logs for password changes. You are looking for password changes on privileged accounts that were not requested by their owners, and for logins to those accounts from unusual places soon after.

If you cannot tell, force a password reset on privileged local accounts and switch administrators to single sign-on where possible, so a local password is not the only route in.

What to do now

  1. Confirm the OvalEdge version and ask the vendor for a fixed release.
  2. Audit recent password changes and logins on privileged accounts.
  3. Reset local administrator passwords and prefer single sign-on for privileged users.
  4. Restrict who can log in to OvalEdge at all, and alert on privileged account changes.

Why it matters

Incorrect authorization (CWE-863) is one of the most common web application flaws. The application checks that you are logged in, but not that you are allowed to act on the object named in the request. Here the object is another user's account.

This class is difficult for scanners that look only for injection patterns, and it is easy for code review to miss. Testing with two accounts, one low privileged and one privileged, finds it quickly.

Because the target is a password, the impact is direct and large: the attacker simply becomes the other user.

Quick check

How is this different from CVE-2022-30357?

Both are account takeover flaws in the same version. This one changes a password directly. The other changes the email address, which is then used with password reset.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.