# CVE-2026-9421: KLiK SocialMediaWebsite File upload.inc.php uniqid unrestricted upload

> Attackers can upload arbitrary files via the file handler, potentially leading to remote code execution on the KLiK SocialMediaWebsite platform.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-fhgp-q8x3-7fx5

## What is CVE-2026-9421?

CVE-2026-9421 is a medium-severity vulnerability in KLiK SocialMediaWebsite, published on 25 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in KLiK SocialMediaWebsite 1.0. This vulnerability affects the function uniqid of the file upload.inc.php of the component File Handler. This manipulation causes unrestricted upload. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-9421?


## How do I fix CVE-2026-9421?

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

## Is CVE-2026-9421 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9421 and fix it if it is affected.

What it is: CVE-2026-9421 is a medium-severity vulnerability in KLiK SocialMediaWebsite, published on 25 May 2026. 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-2026-9421 in the wild and no public exploit code.

Affected product: KLiK SocialMediaWebsite. 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-2026-9421/ (Markdown: https://insights.sbomify.com/CVE-2026-9421/index.md)
```

## Sources

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

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