# CVE-2024-26471: Cross-site scripting in n/a

> Attackers can inject malicious JavaScript into victim browsers via the search parameter in offer.php of the iBarn web application.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Feb 2024
- **Updated:** 27 Aug 2024
- **Also known as:** GHSA-qjr7-7f86-j28r

## What is CVE-2024-26471?

CVE-2024-26471 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A reflected cross-site scripting (XSS) vulnerability in zhimengzhe iBarn v1.5 allows attackers to inject malicious JavaScript into the web browser of a victim via the search parameter in offer.php.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-26471?

It affects 1 product.


Products: Msaad1999 Klik Socialmediawebsite.

## How do I fix CVE-2024-26471?

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

## Is CVE-2024-26471 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-26471 exists.

## Other vulnerabilities in n/a

- [CVE-2024-26472](https://insights.sbomify.com/CVE-2024-26472/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-26473](https://insights.sbomify.com/CVE-2024-26473/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26471 and fix it if it is affected.

What it is: CVE-2024-26471 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-26471 exists.

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-2024-26471/ (Markdown: https://insights.sbomify.com/CVE-2024-26471/index.md)
```

## Sources

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

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