dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-42194

MEDIUM · 6.8 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Admidio is an open-source user management solution. Prior to version 5.0.9, the incomplete SSRF fix in Admidio's fetch_metadata.php validates the resolved IP address but passes the original hostname-based URL to curl_init(), leaving a DNS rebinding TOCTOU window that allows redirecting requests to internal IPs. This issue has been patched in version 5.0.9.

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 confidence

Admidio's fetch_metadata.php has an incomplete SSRF fix where the resolved IP address is validated against internal IP restrictions, but the original hostname-based URL is passed to curl_init(), creating a DNS rebinding TOCTOU window that allows bypassing the validation to access internal infrastructure.

MitigationUpgrade Admidio to version 5.0.9 which contains the complete SSRF fix that properly validates and uses the resolved IP address throughout the request lifecycle.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Admidio installation location
    Locate the Admidio web application directory on the server. Common paths include /var/www/html/admidio, /www/admidio, or check your web server configuration for the document root where Admidio is installed.
    Affected if Admidio is not installed in the expected location or the directory cannot be found.
  2. Check Admidio version
    Open the file admidio/version.php in the installation directory and look for a variable defining the version number (such as $gCurrentSettings->getValue). Compare the installed version to 5.0.9.
    Affected if The installed version is lower than 5.0.9.
  3. Locate fetch_metadata.php
    Search for the file fetch_metadata.php within the Admidio installation directory, typically found under admido/overview/ or admidio/files/ depending on the version.
    Affected if The file fetch_metadata.php exists in the installation.
  4. Inspect the vulnerable code pattern
    Open fetch_metadata.php and examine the code around curl_init(). Look for a pattern where: (1) a hostname URL is passed to gethostbyname() or similar for IP resolution, (2) the resolved IP is validated against internal IP restrictions (e.g., 127.0.0.1, 10.x.x.x, 192.168.x.x), but (3) the original hostname string is still passed to curl_init(). The vulnerability exists if these three conditions are all present.
    Affected if The code shows IP validation on resolved address but curl_init() receives the original hostname variable.

A user is affected if Admidio version is below 5.0.9 AND fetch_metadata.php exists with the TOCTOU pattern where validated IP is bypassed by passing hostname to curl.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Admidio to version 5.0.9 which contains the complete SSRF fix that properly validates and uses the resolved IP address throughout the request lifecycle.

Recommended fix High confidence

5.0.9

  1. 1. Identify the current Admidio installation version (check admidio/version.php or admin panel)
  2. 2. If version is prior to 5.0.9, backup the entire Admidio installation directory and database
  3. 3. Download Admidio version 5.0.9 from the official GitHub releases (github.com/Admidio/Admidio/releases)
  4. 4. Extract the new version and replace files, preserving any custom configurations or uploads directory
  5. 5. Run any database migration scripts included in the upgrade (check docs/ folder or installer)
  6. 6. Verify fetch_metadata.php has been updated and the SSRF fix is applied
  7. 7. Test that the application functions correctly after upgrade
Caveat Review the 5.0.9 release notes for any breaking changes or required configuration updates before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42194 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42194 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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