# CVE-2024-8783: OpenTibiaBR MyAAC Post Reply new_post.php cross site scripting

> Remote attackers can inject malicious scripts via the post_topic argument in the forum reply handler, potentially compromising user sessions.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **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:** 13 Sep 2024
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qf89-78m6-x24m

## What is CVE-2024-8783?

CVE-2024-8783 is a medium-severity cross-site scripting vulnerability in OpenTibiaBR MyAAC, published on 13 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as problematic has been found in OpenTibiaBR MyAAC up to 0.8.16. Affected is an unknown function of the file system/pages/forum/new_post.php of the component Post Reply Handler. The manipulation of the argument post_topic leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The patch is identified as bf6ae3df0d32fa22552bb44ca4f8489a6e78cc1c. It is recommended to apply a patch to fix this issue.

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

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

It affects 1 product.


Products: Opentibiabr Myaac.

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

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

## Is CVE-2024-8783 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8783 is a medium-severity cross-site scripting vulnerability in OpenTibiaBR MyAAC, published on 13 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8783 in the wild and no public exploit code.

Affected product: OpenTibiaBR MyAAC. 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-8783/ (Markdown: https://insights.sbomify.com/CVE-2024-8783/index.md)
```

## Sources

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

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