# CVE-2022-42098: SQL injection in n/a

> An attacker can exploit SQL injection in profile.php to read or modify database contents in KLiK SocialMediaWebsite.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-fwfm-52h5-248x

## What is CVE-2022-42098?

CVE-2022-42098 is a high-severity SQL injection vulnerability in n/a, published on 22 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

KLiK SocialMediaWebsite version v1.0.1 is vulnerable to SQL Injection via the profile.php.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Klik-Socialmediawebsite Project Klik-Socialmediawebsite.

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

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

## Is CVE-2022-42098 being exploited?

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

Public exploit code:

- KLiK-SocialMediaWebsite v1.0.1 has SQL Injection Vulnerabilities at profile.php (github_poc): https://github.com/bypazs/CVE-2022-42098

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42098 is a high-severity SQL injection vulnerability in n/a, published on 22 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-42098 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-42098/ (Markdown: https://insights.sbomify.com/CVE-2022-42098/index.md)
```

## Sources

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

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