# CVE-2019-14467: File upload in n/a

> Attackers can execute arbitrary code by uploading a malicious PHP file as a cover photo in the Social Photo Gallery plugin.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-77pv-pggh-8r9c

## What is CVE-2019-14467?

CVE-2019-14467 is a high-severity vulnerability in n/a, published on 18 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Social Photo Gallery plugin 1.0 for WordPress allows Remote Code Execution by creating an album and attaching a malicious PHP file in the cover photo album, because the file extension is not checked.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2019-14467?

It affects 1 product.


Products: Infoway Social Photo Gallery.

## How do I fix CVE-2019-14467?

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

## Is CVE-2019-14467 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14467 and fix it if it is affected.

What it is: CVE-2019-14467 is a high-severity vulnerability in n/a, published on 18 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-14467 in the wild and no public exploit code.

Affected product: n/a. 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-2019-14467/ (Markdown: https://insights.sbomify.com/CVE-2019-14467/index.md)
```

## Sources

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

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