# CVE-2025-48497: Cross-site request forgery in iroha Board

> Attackers can force logged-in users to register arbitrary learning histories via crafted URLs in iroha Board.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA: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:** 26 Jun 2025
- **Updated:** 26 Jun 2025
- **Also known as:** GHSA-r7vp-cpwx-3ghg

## What is CVE-2025-48497?

CVE-2025-48497 is a medium-severity vulnerability in iroha Board, published on 26 Jun 2025. 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

Cross-site request forgery vulnerability exists in iroha Board versions v0.10.12 and earlier. If a user accesses a specially crafted URL while being logged in to the affected product, arbitrary learning histories may be registered.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Irohasoft Iroha Board.

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

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

## Is CVE-2025-48497 being exploited?

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

## Other vulnerabilities in iroha Board

- [CVE-2025-41404](https://insights.sbomify.com/CVE-2025-41404/): Missing authorization in iroha Board (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48497 is a medium-severity vulnerability in iroha Board, published on 26 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-48497 in the wild and no public exploit code.

Affected product: iroha Board. 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-48497/ (Markdown: https://insights.sbomify.com/CVE-2025-48497/index.md)
```

## Sources

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

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