# CVE-2025-41404: Missing authorization in iroha Board

> Authenticated attackers can view non-public content in iroha Board due to a direct request vulnerability.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/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:** 26 Jun 2025
- **Updated:** 26 Jun 2025
- **Also known as:** GHSA-gcxj-65c6-wcrg

## What is CVE-2025-41404?

CVE-2025-41404 is a medium-severity missing authorization vulnerability in iroha Board, published on 26 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Direct request ('Forced Browsing') issue exists in iroha Board versions v0.10.12 and earlier. If this vulnerability is exploited, non-public contents may be viewed by an attacker who can log in to the affected product.

Weakness: CWE-425 (Direct Request)

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

It affects 1 product.


Products: Irohasoft Iroha Board.

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

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

## Is CVE-2025-41404 being exploited?

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

## Other vulnerabilities in iroha Board

- [CVE-2025-48497](https://insights.sbomify.com/CVE-2025-48497/): Cross-site request forgery in iroha Board (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41404 is a medium-severity missing authorization vulnerability in iroha Board, published on 26 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41404 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-41404/ (Markdown: https://insights.sbomify.com/CVE-2025-41404/index.md)
```

## Sources

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

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