Skip to main content
CVE-2025-11222VulnerabilityPublished

CVE-2025-11222: LINE Central Dogma · na

Affects LINE Central DogmaSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium · fixed in 0.78.0 : update LINE Central Dogma when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.78.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
GitHubline/centraldogmapkg:github/line/centraldogmaOther threatsAffected
  • =0.77
Fixed in–

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

AI-suggested

1. Upgrade Central Dogma to version 0.78.0 or later immediately, as this version addresses the Open Redirect vulnerability. 2. Implement strict validation and sanitization of all URL parameters used for redirection to ensure only trusted domains are allowed. 3. Employ Content Security Policy (CSP) headers to restrict the domains to which users can be redirected. 4. Educate users and administrators about the risks of phishing and the importance of scrutinizing URLs before clicking, especially those originating from Central Dogma interfaces. 5. Monitor logs and network traffic for unusual redirect patterns or spikes in user redirection requests. 6. Use multi-factor authentication (MFA) to reduce the impact of credential theft resulting from phishing. 7. Consider deploying web application firewalls (WAFs) with rules to detect and block suspicious redirect attempts. 8. Conduct regular security assessments and penetration tests focusing on URL handling and redirection logic in Central Dogma deployments.

Description

Central Dogma versions before 0.78.0 contain an Open Redirect vulnerability that allows attackers to redirect users to untrusted sites via specially crafted URLs, potentially facilitating phishing attacks and credential theft.

References

Community reviews

Loading reviews…