CVE-2025-48497VulnerabilityPublished 26 Jun 2025

CVE-2025-48497: iroha Board · Cross-site request forgery (CSRF)

Affects iroha BoardSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
iroha Soft Co., Ltd. iroha Board	Affected <=0.10.12	Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should implement the following specific measures: 1) Apply any available updates or patches from iroha Soft Co., Ltd. as soon as they are released. 2) If patches are not yet available, deploy web application firewalls (WAFs) with rules to detect and block suspicious CSRF attempts targeting iroha Board endpoints. 3) Enforce strict Content Security Policy (CSP) headers to reduce the risk of malicious external content triggering CSRF. 4) Educate users on the risks of clicking unknown or suspicious links, especially while logged into iroha Board. 5) Implement additional CSRF tokens or anti-CSRF mechanisms at the application level if customization is possible, ensuring that state-changing requests require a valid token. 6) Monitor logs for unusual activity related to learning history modifications to detect potential exploitation attempts. 7) Limit session lifetimes and enforce re-authentication for sensitive actions to reduce the window of opportunity for attackers. These targeted actions go beyond generic advice by focusing on both technical controls and user awareness specific to the nature of this vulnerability.

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.

Impact

For European organizations using iroha Board, this vulnerability primarily threatens the integrity of learning history data, which could affect training records, compliance tracking, or user progress monitoring. While it does not compromise sensitive data confidentiality or system availability, the unauthorized modification of learning histories could disrupt organizational workflows, lead to inaccurate reporting, and undermine trust in the system's data accuracy. In sectors such as education, corporate training, or compliance-heavy industries, this could have regulatory or operational repercussions. Since exploitation requires user interaction (the user must be logged in and visit a malicious URL), phishing or social engineering campaigns could be used to trigger the vulnerability. The impact is more pronounced in environments where iroha Board is integrated into critical learning management or compliance systems, as corrupted data may lead to incorrect decisions or audit failures.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Jun 2025, 06:41 UTC

Technical details

References

Community reviews

Related threats