VulnerabilityPublished 10 Nov 2025Updated 24 Feb 2026

CVE-2025-12925: rymcu forest · Missing Authorization

Affects rymcu forestSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Nov 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

AI-suggested

To mitigate CVE-2025-12925, organizations should immediately conduct a thorough code audit of the UserDicController.java file and related API endpoints to implement strict authorization checks ensuring only authorized users can access getAll, addDic, getAllDic, and deleteDic functions. Employ role-based access control (RBAC) or attribute-based access control (ABAC) mechanisms to enforce permissions. Network-level controls such as firewall rules or API gateways should restrict access to these endpoints to trusted internal networks or authenticated clients only. Enable detailed logging and monitoring of API calls to detect anomalous or unauthorized access attempts. Since the product uses a rolling release model, maintain close communication with the rymcu project maintainers to receive timely patches or updates. If patches are unavailable, consider temporary workarounds such as disabling or restricting these API functions until proper authorization is enforced. Additionally, conduct penetration testing focused on authorization bypass scenarios to validate the effectiveness of implemented controls. Educate development teams on secure coding practices to prevent similar authorization flaws in future releases.

Description

A security flaw has been discovered in rymcu forest up to de53ce79db9faa2efc4e79ce1077a302c42a1224. Impacted is the function getAll/addDic/getAllDic/deleteDic of the file src/main/java/com/rymcu/forest/lucene/api/UserDicController.java. The manipulation results in missing authorization. The attack may be launched remotely. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases.

Impact

The missing authorization vulnerability allows remote attackers to bypass access controls on critical API functions managing user dictionary data. This can lead to unauthorized disclosure of sensitive information, unauthorized modification or deletion of user dictionary entries, and potential disruption of application functionality relying on this data. For organizations, this could result in data integrity violations, loss of trust in the application, and potential compliance issues if sensitive user data is exposed or altered. Since no authentication is required, attackers can exploit this vulnerability from anywhere on the network, increasing the attack surface. The rolling release nature of the product may delay patch deployment, prolonging exposure. While no active exploitation is currently known, the vulnerability's characteristics make it a likely target for attackers seeking to manipulate or exfiltrate data without detection. Organizations relying on rymcu forest for critical operations or handling sensitive data are at heightened risk of operational disruption and data breaches.

Summary

CVE-2025-12925 identifies a missing authorization vulnerability in the rymcu forest project, specifically impacting the UserDicController.java file's functions: getAll, addDic, getAllDic, and deleteDic. These functions handle user dictionary operations within the application. Due to the lack of proper authorization checks, an attacker can remotely invoke these API endpoints to retrieve, add, or delete dictionary entries without any authentication or user interaction. The vulnerability arises from insufficient access control mechanisms in the code, allowing unauthorized manipulation of potentially sensitive user dictionary data. The product follows a rolling release development model, which means there are no discrete version numbers to identify affected or patched releases, complicating patch management. The CVSS 4.0 vector indicates a network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), and no user interaction (UI:N), with limited impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). No known exploits have been reported in the wild, but the vulnerability presents a significant risk due to its ease of exploitation and potential for unauthorized data manipulation. The lack of authorization enforcement in these critical API functions could lead to data integrity issues and unauthorized data disclosure within affected deployments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:19 UTC

Technical details

References

Community reviews

Related threats