# CVE-2015-1376: Server-side request forgery in n/a

> Authenticated users can write arbitrary files via SSRF in the Pixabay Images plugin, potentially leading to code execution.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r6rj-wrr3-48q3

## What is CVE-2015-1376?

CVE-2015-1376 is a medium-severity server-side request forgery vulnerability in n/a, published on 28 Jan 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

pixabay-images.php in the Pixabay Images plugin before 2.4 for WordPress does not validate hostnames, which allows remote authenticated users to write to arbitrary files via an upload URL with a host other than pixabay.com.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2015-1376?

It affects 1 product.


Products: Pixabay Images Project Pixabay Images.

## How do I fix CVE-2015-1376?

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

## Is CVE-2015-1376 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-1376 exists.

Public exploit code:

- WordPress Pixabay Images PHP Code Upload (metasploit)
- WordPress Plugin Pixarbay Images 2.3 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2015-1375](https://insights.sbomify.com/CVE-2015-1375/): Missing authorization in n/a (high 7.5)
- [CVE-2015-1365](https://insights.sbomify.com/CVE-2015-1365/): Path traversal in n/a (medium 5.0)
- [CVE-2015-1366](https://insights.sbomify.com/CVE-2015-1366/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1376 and fix it if it is affected.

What it is: CVE-2015-1376 is a medium-severity server-side request forgery vulnerability in n/a, published on 28 Jan 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-1376 exists.

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-2015-1376/ (Markdown: https://insights.sbomify.com/CVE-2015-1376/index.md)
```

## Sources

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

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