# CVE-2025-29621: Other in n/a

> Attackers can manipulate application settings via content spoofing in the Theme configuration module of RosarioSIS.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2025
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-25f3-5qr3-55jw

## What is CVE-2025-29621?

CVE-2025-29621 is a high-severity vulnerability in n/a, published on 22 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Francois Jacquet RosarioSIS v12.0.0 was discovered to contain a content spoofing vulnerability in the Theme configuration under the My Preferences module. This vulnerability allows attackers to manipulate application settings.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2025-29621 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-29621 is a high-severity vulnerability in n/a, published on 22 Apr 2025. 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-2025-29621 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-29621/ (Markdown: https://insights.sbomify.com/CVE-2025-29621/index.md)
```

## Sources

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

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