CVE-2019-11066
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 · uneditedopenid.php in LightOpenID through 1.3.1 allows SSRF via a crafted OpenID 2.0 assertion request using the HTTP GET method.
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 confidenceLightOpenID library through version 1.3.1 contains an SSRF vulnerability in openid.php where a crafted OpenID 2.0 assertion request via HTTP GET allows attackers to force the server to make requests to arbitrary URLs, potentially accessing internal services, cloud metadata endpoints, or internal network resources.
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<= 1.3.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate LightOpenID library filesSearch the codebase for files named 'openid.php' or directories containing 'lightopenid' or 'openid' in the name. Common locations include vendor/, lib/, or project-specific directories.Affected if The library files are present in the environment
-
Identify the installed versionCheck for a version file, composer.json, or the header comments in openid.php for a version number. Compare against the affected range: versions 1.3.1 and below.Affected if The version is 1.3.1 or lower, or no version is found (indicating an older release)
-
Verify openid.php is accessibleCheck if openid.php is exposed via the web server. Look for URL patterns like /openid.php, /lib/openid.php, or similar paths that may handle OpenID requests.Affected if openid.php is accessible via HTTP/HTTPS and can receive GET parameters
-
Confirm OpenID 2.0 consumer is in useReview the application code to determine if OpenID 2.0 authentication is implemented. Look for OpenID 2.0 identifier submissions or 'openid_identifier' GET/POST parameters being processed.Affected if The application uses OpenID 2.0 (as opposed to OpenID Connect or other auth methods)
-
Check for URL validation on OpenID requestsInspect openid.php for URL validation logic before making HTTP requests. Look for allowlist checks or URL scheme validation on the endpoint being requested.Affected if No URL allowlist or strict validation is performed before fetching OpenID endpoints
A user is affected if LightOpenID version 1.3.1 or lower is installed, openid.php handles OpenID 2.0 requests, and no URL validation exists on the OpenID endpoint fetcher.
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.
From vendor dataUpgrade LightOpenID to a patched version. If no patched version is available, implement URL allowlist validation and restrict outbound connections from the server via firewall or WAF rules.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11066 — 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-2019-11066 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