CVE-2026-3013
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 · uneditedCoppermine Photo Gallery in versions 1.6.09 through 1.6.27 is vulnerable to path traversal. Unauthenticated remote attacker is able to exploit a vulnerable endpoint and construct payloads that allow to read content of any file accessible by the the web server process.This issue was fixed in version 1.6.28.
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 confidenceCoppermine Photo Gallery versions 1.6.09-1.6.27 contains a path traversal vulnerability in an unauthenticated endpoint. Attackers can use directory traversal sequences (e.g., ../) to read arbitrary files accessible to the web server process, potentially exposing sensitive system files, configuration credentials, or application source code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Identify Coppermine Photo Gallery installationSearch for 'coppermine' or 'cpg' directories in the web root, or look for the characteristic index.php with Coppermine brandingAffected if Coppermine Photo Gallery is present on the server
-
Determine installed versionCheck the version.php file in the Coppermine root directory, typically contains a version constant like define('CPG_VERSION', 'x.x.xx') or check any version file within the installationAffected if Version is 1.6.09 through 1.6.27 inclusive
-
Confirm unauthenticated access is possibleVerify the web server allows unauthenticated requests to the vulnerable endpoint (no login required to access the path traversal functionality)Affected if The vulnerable endpoint does not require authentication
-
Locate the vulnerable endpointIdentify the unauthenticated endpoint that handles file operations or parameter handling susceptible to directory traversal sequencesAffected if An unauthenticated endpoint accepting user-controlled file paths is present and accessible
Your environment is affected if Coppermine Photo Gallery version 1.6.09 through 1.6.27 is installed and an unauthenticated endpoint handling file paths is exposed.
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.
dbcve · scopedUpgrade to version 1.6.28 or later immediately. If immediate upgrade is not feasible, restrict the web server process file system permissions and consider temporarily blocking unauthenticated access to vulnerable endpoints at the network level.
1.6.28
- Download Coppermine Photo Gallery version 1.6.28 from the official source
- Replace the existing installation files with the new version
- Verify the upgrade was successful by checking the version number in the admin panel
- Ensure the web server has appropriate file permissions after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3013 — 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-2026-3013 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