CVE-2025-11222
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCentral 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCentral Dogma versions before 0.78.0 contain an Open Redirect vulnerability where the application fails to properly validate redirect URLs, allowing attackers to craft malicious URLs that appear to originate from the trusted domain but redirect users to arbitrary external sites. This can be exploited to conduct phishing attacks and credential theft.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.78.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Central Dogma installationCheck for Central Dogma processes running or installed on the system. Common locations include /opt/central-dogma, /usr/local/central-dogma, or check running Java processes for central-dogma.Affected if Central Dogma is found running or installed on the system
-
Determine installed versionLocate the version file or check the build manifest. Common approaches: check a version file in the installation directory, examine the JAR file name, or query the running process for version information if the application exposes a version endpoint.Affected if The version cannot be determined or is less than 0.78.0
-
Compare version to affected rangeParse the version number and compare against 0.78.0 using semantic versioning rules. Any version below 0.78.0 (such as 0.77.0, 0.76.0, etc.) is affected.Affected if Installed version is less than 0.78.0
If Central Dogma is present and the installed version is below 0.78.0, the environment is vulnerable to the open redirect flaw described in CVE-2025-11222.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.78.0
Upgrade Central Dogma to version 0.78.0 or later to obtain the security patch that addresses the open redirect vulnerability.
0.78.0
- 1. Back up your current Central Dogma installation and configuration
- 2. Consult the official Central Dogma release notes or changelog for version 0.78.0 to understand changes
- 3. Download the version 0.78.0 release from the official Central Dogma repository (github.com)
- 4. Stop the running Central Dogma service
- 5. Install version 0.78.0 following the standard upgrade procedure for your deployment method
- 6. Verify the installation and test that the service starts correctly
- 7. Confirm the open redirect vulnerability is resolved by testing with the previously vulnerable URL patterns
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11222 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11222 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data