dbcve.org
Coppermine Photo GalleryApplication · Coppermine Gallery

CVE-2005-3979

MEDIUM · 5.0 CVSS v2.0 Published 2005-12-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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
relocate_server.php in Coppermine Photo Gallery (CPG) 1.4.2 and 1.4 beta is not removed after installation and does not use authentication, which allows remote attackers to obtain sensitive information, such as database configuration, via a direct request.

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

The relocate_server.php script in Coppermine Photo Gallery versions 1.4.2 and 1.4 beta was not removed after the installation/migration process. This script exposes sensitive information, including database configuration credentials, without requiring any authentication, allowing remote attackers to directly request and obtain this data.

MitigationDelete the relocate_server.php file from the web server after completing any server migration or installation. Verify the file is not present in production environments.

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
Coppermine Photo GalleryApplication
Affected:= 1.4= 1.4.2

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
None

AV:N/AC:L/Au:N/C:P/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. Locate relocate_server.php file
    Search the web server file system for the file relocate_server.php within the Coppermine installation directory and any subdirectories
    Affected if The file exists in the Coppermine installation folder
  2. Check web accessibility
    Attempt to request http(s)://your-server/path/to/coppermine/relocate_server.php via HTTP request from a browser or curl command
    Affected if The file returns a response (even an error page) indicating it is accessible via the web
  3. Verify sensitive data exposure
    If the file is accessible, examine the output for database host, username, password, or database name strings
    Affected if The file output contains plaintext database credentials or configuration values

If the relocate_server.php file exists and is web-accessible, the environment is vulnerable and sensitive database credentials can be obtained without authentication.

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

Delete the relocate_server.php file from the web server after completing any server migration or installation. Verify the file is not present in production environments.

Fix this in Coppermine Photo Gallery Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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