# CVE-2014-4648: Unspecified vulnerability in Piwigo before 2.6.3 has unknown impact and attack vectors, related to a "security failure."


- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gfq7-6cj8-hv9f

## What is CVE-2014-4648?

CVE-2014-4648 is a critical vulnerability in Piwigo Piwigo, published on 28 Jun 2014. 

### Official description

Unspecified vulnerability in Piwigo before 2.6.3 has unknown impact and attack vectors, related to a "security failure."

## Which versions are affected by CVE-2014-4648?

It affects 1 product.


Products: Piwigo Piwigo.

## How do I fix CVE-2014-4648?

No fix has been published for CVE-2014-4648 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-4648 being exploited?

There is no known exploitation of CVE-2014-4648 in the wild and no public exploit code.

## Other vulnerabilities in Piwigo Piwigo

- [CVE-2023-33361](https://insights.sbomify.com/CVE-2023-33361/): SQL injection in n/a (critical 9.8)
- [CVE-2023-33362](https://insights.sbomify.com/CVE-2023-33362/): SQL injection in n/a (critical 9.8)
- [CVE-2020-19213](https://insights.sbomify.com/CVE-2020-19213/): SQL injection in n/a (critical 9.8)
- [CVE-2021-32615](https://insights.sbomify.com/CVE-2021-32615/): SQL injection in n/a (critical 9.8)
- [CVE-2017-10682](https://insights.sbomify.com/CVE-2017-10682/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-4648 and fix it if it is affected.

What it is: CVE-2014-4648 is a critical vulnerability in Piwigo Piwigo, published on 28 Jun 2014. 
Exploitation: There is no known exploitation of CVE-2014-4648 in the wild and no public exploit code.

Affected product: Piwigo Piwigo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-4648/ (Markdown: https://insights.sbomify.com/CVE-2014-4648/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-4648
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-4648
- OSV: https://osv.dev/vulnerability/CVE-2014-4648

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-4648/
Summaries are generated and may contain mistakes; the official description above is the record.