# CVE-2014-7860: Missing authorization in n/a

> Remote attackers can access and publish arbitrary photos to Facebook profiles without authentication due to missing checks in the publish script.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gmcr-cvch-ppg6

## What is CVE-2014-7860?

CVE-2014-7860 is a medium-severity missing authorization vulnerability in n/a, published on 25 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web/web_file/fb_publish.php script in D-Link DNS-320L before 1.04b12 and DNS-327L before 1.03b04 Build0119 does not authenticate requests, which allows remote attackers to obtain arbitrary photos and publish them to an arbitrary Facebook profile via a target album_id and access_token.

Weakness: CWE-287 (Improper Authentication), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 2 products.


Products: D-Link Dns-320l Firmware, D-Link Dns-327l Firmware.

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

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

## Is CVE-2014-7860 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-7860 is a medium-severity missing authorization vulnerability in n/a, published on 25 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-7860 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-2014-7860/ (Markdown: https://insights.sbomify.com/CVE-2014-7860/index.md)
```

## Sources

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

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