dbcve.org
Coppermine GalleryApplication

CVE-2010-4815

CRITICAL · 9.8 CVSS v3.1 Published 2020-02-05
Fix available
A fix is available. Upgrade to 1.4.26 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Coppermine gallery before 1.4.26 has an input validation vulnerability that allows for code execution.

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

Coppermine Gallery versions prior to 1.4.26 contain an input validation vulnerability that allows remote attackers to execute arbitrary code. The vulnerability stems from insufficient sanitization of user-supplied input, likely in a parameter processed by PHP, enabling attackers to inject and execute malicious commands on the host system.

MitigationUpgrade to Coppermine Gallery version 1.4.26 or later, which contains the patched input validation. If immediate patching is not feasible, implement web application firewall rules to block suspicious input patterns and restrict file upload capabilities as a compensating control.

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 GalleryApplication
Affected:< 1.4.26

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

CVSS:3.1/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 checks

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

  1. Verify Coppermine Gallery version
    Locate the version file in your Coppermine installation (typically includes/version.php or check the admin panel for version info) and compare it to 1.4.26
    Affected if The installed version is below 1.4.26 (e.g., 1.4.25, 1.4.24, etc.)
  2. Confirm Coppermine is web-accessible
    Check if the Coppermine Gallery directory is accessible via HTTP/HTTPS on your web server
    Affected if The application is exposed on the web and accepts user input through web requests
  3. Check for user input processing modules
    Identify PHP scripts that handle user-supplied parameters (common targets include search functions, album parameters, or upload handlers) and verify they process unsanitized input
    Affected if User-controllable parameters are passed to PHP functions without proper sanitization (such as eval, system, exec, or unsanitized database queries)
  4. Review PHP configuration
    Examine php.ini for dangerous function settings (disable_functions should include system, exec, passthru, shell_exec if not needed) and verify allow_url_fopen and include handling
    Affected if PHP is configured with dangerous functions enabled and the application processes user input through them

Your environment is affected if Coppermine Gallery version is below 1.4.26 AND the application is web-accessible with user input being processed by PHP code lacking proper sanitization.

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
Upgrade available Upgrade to 1.4.26 or later
Fixed in 1.4.26
Interim mitigation

Upgrade to Coppermine Gallery version 1.4.26 or later, which contains the patched input validation. If immediate patching is not feasible, implement web application firewall rules to block suspicious input patterns and restrict file upload capabilities as a compensating control.

Recommended fix Moderate confidence

Coppermine Gallery 1.4.26

  1. 1. Back up the Coppermine Gallery database and all website files
  2. 2. Download Coppermine Gallery version 1.4.26 from the official source (forum.coppermine-gallery.net)
  3. 3. Extract the archive and replace existing Coppermine files on the server
  4. 4. Run any included upgrade scripts or database migration tools
  5. 5. Verify the upgrade was successful by accessing the gallery and testing functionality

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

Fix this in Coppermine Gallery Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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