# CVE-2014-9516: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via the PATH_INFO in the Profile section, requiring user interaction to execute.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Jan 2015
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-88p6-3p2j-mvhv

## What is CVE-2014-9516?

CVE-2014-9516 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Jan 2015. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in Social Microblogging PRO 1.5 allows remote attackers to inject arbitrary web script or HTML via the PATH_INFO to the default URI, related to the "Web Site" input in the Profile section.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Social Microblogging Pro Project Social Microblogging Pro.

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

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

## Is CVE-2014-9516 being exploited?

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

Public exploit code:

- Social Microblogging PRO 1.5 - Persistent Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-9516 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Jan 2015. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-9516 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-2014-9516/ (Markdown: https://insights.sbomify.com/CVE-2014-9516/index.md)
```

## Sources

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

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