# CVE-2022-22792: MobiSoft - MobiPlus User Take Over and Improper Handling of url Parameters

> Attackers can access a specific URL to view all user credentials in clear text, leading to potential account takeover.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Feb 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-m784-mvqp-pvw3

## What is CVE-2022-22792?

CVE-2022-22792 is a medium-severity vulnerability in MobiSoft eharmony, published on 16 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

MobiSoft - MobiPlus User Take Over and Improper Handling of url Parameters Attacker can navigate to specific url which will expose all the users and password in clear text. http://IP/MobiPlusWeb/Handlers/MainHandler.ashx?MethodName=GridData&GridName=Users

Weakness: CWE-233 (Improper Handling of Parameters)

## Which versions are affected by CVE-2022-22792?

It affects 1 product.


Products: Mobisoft - Mobiplus Project Mobisoft - Mobiplus.

## How do I fix CVE-2022-22792?

No fix has been published for CVE-2022-22792 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-22792 being exploited?

There is no known exploitation of CVE-2022-22792 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22792 and fix it if it is affected.

What it is: CVE-2022-22792 is a medium-severity vulnerability in MobiSoft eharmony, published on 16 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-22792 in the wild and no public exploit code.

Affected product: MobiSoft eharmony. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-22792/ (Markdown: https://insights.sbomify.com/CVE-2022-22792/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-22792
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-22792
- OSV: https://osv.dev/vulnerability/CVE-2022-22792

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-22792/
Summaries are generated and may contain mistakes; the official description above is the record.