CVE-2025-44091VulnerabilityPublished 12 Jun 2025

CVE-2025-44091: crud · n/a

Affects crudSource CVE Database V5

Not known to be exploited.

Data as of 26 Oct 2026, 06:26 UTC

Severity

High

Rated High by the CNA (mitre) · No CVSS score from NVD or the CNA

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

Exploitation evidence

Disclosed: evidence found.
CVE published 12 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-26.

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
GitHubyangyouwang/crud`pkg:github/yangyouwang/crud`Other threats	Affected =1.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations should first identify all instances of yangyouwang crud v1.0.0 in their environments, focusing on those with role management enabled. Until an official patch is released, organizations should implement strict input validation and output encoding on the role management inputs to neutralize malicious scripts. Employing Content Security Policy (CSP) headers can reduce the risk of script execution by restricting the sources of executable scripts. Access to the role management interface should be limited to the minimum necessary users, ideally through network segmentation and multi-factor authentication to reduce the attack surface. Regular security audits and penetration testing focusing on XSS vulnerabilities in administrative modules are recommended. Monitoring web application logs for suspicious input patterns or anomalous user behavior can help detect attempted exploitation. Finally, organizations should maintain awareness of updates from the vendor or security community regarding patches or workarounds and apply them promptly once available.

Description

yangyouwang crud v1.0.0 is vulnerable to Cross Site Scripting (XSS) via the role management function.

Impact

For European organizations using yangyouwang crud v1.0.0, this XSS vulnerability in the role management function poses several risks. If exploited, attackers could execute malicious scripts in the browsers of users with access to the role management interface, potentially leading to theft of session tokens, unauthorized role changes, or lateral movement within the application. This could compromise the confidentiality and integrity of sensitive data managed by the CRUD system, especially if it is used in environments handling personal data subject to GDPR regulations. The availability impact is generally low for XSS but could escalate if attackers leverage the vulnerability to deploy further attacks or disrupt administrative functions. The threat is heightened in sectors where role management controls access to critical systems or sensitive data, such as finance, healthcare, or government agencies. Given the lack of known exploits, the immediate risk may be moderate, but the presence of an unpatched XSS in an administrative function warrants prompt attention to prevent potential targeted attacks. Additionally, exploitation could facilitate phishing or social engineering campaigns by injecting malicious content into trusted administrative interfaces.

References

Community reviews

Loading reviews…