# CVE-2025-61228: Code injection in n/a

> A local attacker can execute arbitrary code via the software update mechanism in SuperDuper!, requiring users to upgrade to a patched version.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-cq93-6j46-hpvh

## What is CVE-2025-61228?

CVE-2025-61228 is a high-severity code injection vulnerability in n/a, published on 1 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in Shirt Pocket SuperDuper! V.3.10 and before allows a local attacker to execute arbitrary code via the software update mechanism

Weakness: CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2025-61228?

It affects 1 product.


Products: Shirt-Pocket Superduper\!.

## How do I fix CVE-2025-61228?

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

## Is CVE-2025-61228 being exploited?

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

Public exploit code:

- https://github.com/graypixel2121/CVE-2025-61228 (github_poc): https://github.com/graypixel2121/CVE-2025-61228

## Other vulnerabilities in n/a

- [CVE-2025-61229](https://insights.sbomify.com/CVE-2025-61229/): Privilege escalation in n/a (high 8.4)
- [CVE-2025-57489](https://insights.sbomify.com/CVE-2025-57489/): Privilege escalation in n/a (high 8.1)
- [CVE-2025-69604](https://insights.sbomify.com/CVE-2025-69604/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61228 and fix it if it is affected.

What it is: CVE-2025-61228 is a high-severity code injection vulnerability in n/a, published on 1 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-61228 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-2025-61228/ (Markdown: https://insights.sbomify.com/CVE-2025-61228/index.md)
```

## Sources

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

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