# CVE-2022-28607: Information disclosure in n/a

> Attackers can gain sensitive information via the action parameter in the user module controller of the ISIC tour booking application.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-g76x-m5qr-8rc7

## What is CVE-2022-28607?

CVE-2022-28607 is a high-severity vulnerability in n/a, published on 1 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in asith-eranga ISIC tour booking through version published on Feb 13th 2018, allows attackers to gain sensitive information via the action parameter to /system/user/modules/mod_users/controller.php.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Isic.lk Project Isic.lk.

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

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

## Is CVE-2022-28607 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-30528](https://insights.sbomify.com/CVE-2022-30528/): SQL injection in n/a (critical 9.8)
- [CVE-2022-30529](https://insights.sbomify.com/CVE-2022-30529/): File upload in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28607 is a high-severity vulnerability in n/a, published on 1 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-28607 in the wild and no public exploit code.

Affected product: n/a. 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-28607/ (Markdown: https://insights.sbomify.com/CVE-2022-28607/index.md)
```

## Sources

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

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