GalleryApplication · Menalto

CVE-2007-6692

MEDIUM · 6.4 CVSS v2.0 Published 2008-01-17
Fix available
A fix is available. Upgrade to after 2.2.3 or later.
See remediation →
73/100
Remediation priority · Elevated
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
Open redirect vulnerability in Menalto Gallery before 2.2.4 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the (1) Core and (2) print modules.

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

Open redirect vulnerability in Menalto Gallery versions prior to 2.2.4 allows remote attackers to redirect users to arbitrary external websites via a URL parameter in the Core and print modules. This occurs because the application does not properly validate or restrict redirect destinations, enabling phishing attacks where users believe they remain on the legitimate site.

MitigationUpgrade to Gallery 2.2.4 or later. If upgrading is not immediately feasible, implement input validation to restrict redirect URLs to same-domain destinations only, rejecting any URL containing external domains or suspicious patterns.

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
GalleryApplication
Affected:<= 2.2.3

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
None
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:N/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. Confirm Menalto Gallery installation
    Locate the Gallery installation directory and check for the version file or access the admin panel to view the version number
    Affected if Gallery is installed and version is 2.2.3 or lower
  2. Verify affected module status
    Access the Gallery admin panel and navigate to the Modules section to list enabled modules
    Affected if Core module or print module is enabled (these are enabled by default in most installations)
  3. Identify vulnerable redirect parameter
    Examine the codebase for the redirect URL parameter handling in Core and print modules, typically in files like redirect.php or functions handling return URLs
    Affected if The application accepts a redirect parameter without validating that the destination is on the same domain
  4. Test redirect behavior
    Craft a URL with an external redirect target (e.g., adding a return parameter pointing to http://example.com) and observe if the application redirects to that external site
    Affected if The application redirects to external domains without warning or confirmation

You are affected if Gallery version is 2.2.3 or earlier AND either the Core or print module is enabled, with the application allowing unvalidated external redirect URLs.

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
Upgrade available Upgrade to a release after 2.2.3
Interim mitigation

Upgrade to Gallery 2.2.4 or later. If upgrading is not immediately feasible, implement input validation to restrict redirect URLs to same-domain destinations only, rejecting any URL containing external domains or suspicious patterns.

Fix this in Gallery Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-6692 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