# CVE-2024-13073: XSS in Akinsoft's TaskPano

> An attacker can inject malicious scripts into TaskPano pages, potentially stealing user sessions or executing code in victim browsers.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2025
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-9wmv-2c7p-59qw

## What is CVE-2024-13073?

CVE-2024-13073 is a medium-severity cross-site scripting vulnerability in Akinsoft TaskPano, published on 4 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Akinsoft TaskPano allows Cross-Site Scripting (XSS).

This issue affects TaskPano: s1.06.04.

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

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


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

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

## Is CVE-2024-13073 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13073 is a medium-severity cross-site scripting vulnerability in Akinsoft TaskPano, published on 4 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13073 in the wild and no public exploit code.

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

## Sources

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

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