CVE-2025-48497: Cross-site request forgery vulnerability exists in iroha Board versions v0.10.12 and earlier
CVE-2025-48497 is a medium-severity flaw (CVSS 4.3) affecting iroha board. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- No elevated risk signals yet
A fixed release or distro patch exists.
Risk facts
| CVSS score | 4.3 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.1% (top 96%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2025-06-26 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-48497?
iroha board: upgrade to 0.10.13. Exact commands for each OS are on this page.
Is CVE-2025-48497 being exploited?
CVE-2025-48497 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-48497 affect?
CVE-2025-48497 affects iroha board. Severity is medium (CVSS 4.3). 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.
How urgent is CVE-2025-48497?
Priority 16/100. No elevated risk signals yet.
Related CVEs
- CVE-2025-41404 MEDIUM 4.3 UPGRADE Direct request ('Forced Browsing') issue exists in iroha Board versions v0.10.12 and earlier