dbcve.org
OpenidApplication

CVE-2007-1652

HIGH · 7.5 CVSS v2.0 Published 2007-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
OpenID allows remote attackers to forcibly log a user into an OpenID enabled site, divulge the user's personal information to this site, and add it site to the trusted sites list via a crafted web page, related to cached tokens.

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 · moderate confidence

This OpenID vulnerability allows remote attackers to exploit cached authentication tokens. By crafting a malicious web page, an attacker can force a user's browser to reuse cached tokens, enabling unauthorized login to OpenID-enabled sites, unauthorized access to the user's personal information, and modification of the user's trusted sites list.

MitigationImplement proper token expiration and invalidation mechanisms, ensure tokens are bound to specific realms, and add CSRF protections to prevent forced token reuse. Additionally, validate token uniqueness and implement secure token storage practices.

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
OpenidApplication
Affected:all versions

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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. Verify OpenID consumer/provider is in use
    Search your codebase, application configuration files, and installed packages for OpenID-related libraries (e.g., python-openid, openid consumer, openid provider) and confirm the OpenID authentication module is enabled.
    Affected if OpenID authentication is actively used in the application and tokens are being issued or consumed.
  2. Inspect token caching configuration
    Review application configuration files, session settings, and authentication middleware to locate where OpenID tokens are cached. Look for cache storage mechanisms (database, memory, file-based) and check if tokens are stored without time-based expiration.
    Affected if Tokens are cached with no expiration or with excessively long cache durations that allow reuse beyond intended sessions.
  3. Confirm token realm binding
    Examine the OpenID library or application code that handles token generation and validation. Check if tokens include a realm or audience field that binds them to a specific relying party URL or identifier.
    Affected if Tokens are generated without realm binding, allowing them to be valid across different relying parties.
  4. Check for token uniqueness validation
    Review the token validation logic to determine if the system checks for token uniqueness (e.g., replay attack prevention, nonce usage) when processing incoming OpenID authentication responses.
    Affected if The validation process does not verify token uniqueness, allowing the same token to be replayed.
  5. Inspect CSRF protection on OpenID endpoints
    Locate the OpenID consumer endpoint handling authentication responses. Verify that CSRF tokens or equivalent protections are required for state-changing operations related to token processing.
    Affected if No CSRF protection exists on OpenID authentication endpoints, enabling forced token reuse attacks.

A user is affected if their OpenID implementation uses uncached or persistently cached tokens without realm binding, lacks token uniqueness validation, and missing CSRF protections on authentication endpoints.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper token expiration and invalidation mechanisms, ensure tokens are bound to specific realms, and add CSRF protections to prevent forced token reuse. Additionally, validate token uniqueness and implement secure token storage practices.

Fix this in Openid Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-1652 — 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-2007-1652 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