# CVE-2011-4595: Cross-site scripting in pretty-link plugin

> Cross-site scripting vulnerability in Pretty-Link WordPress plugin allows attackers to inject malicious scripts, potentially leading to session hijacking or code execution.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jan 2020
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8hr8-h5jx-w7gp

## What is CVE-2011-4595?

CVE-2011-4595 is a medium-severity cross-site scripting vulnerability in pretty-link plugin, published on 10 Jan 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Pretty-Link WordPress plugin 1.5.2 has XSS

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

## Which versions are affected by CVE-2011-4595?

It affects 1 product.


Products: Caseproof Prettylinks.

## How do I fix CVE-2011-4595?

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

## Is CVE-2011-4595 being exploited?

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

Public exploit code:

- WordPress Plugin Pretty Link 1.5.2 - 'pretty-bar.php' Cross-Site Scripting (exploitdb)

## Other vulnerabilities in pretty-link plugin

- [CVE-2015-9457](https://insights.sbomify.com/CVE-2015-9457/): SQL injection in n/a (high 7.2)
- [CVE-2024-2326](https://insights.sbomify.com/CVE-2024-2326/): Cross-site request forgery in PrettyLinks – Affiliate Links, Link Branding, Link Tracking, Marketing and Stripe Payments Plugin (medium 4.3)
- [CVE-2013-1636](https://insights.sbomify.com/CVE-2013-1636/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4595 and fix it if it is affected.

What it is: CVE-2011-4595 is a medium-severity cross-site scripting vulnerability in pretty-link plugin, published on 10 Jan 2020. An attacker can exploit it over the internet without logging in, 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-2011-4595 exists.

Affected product: pretty-link plugin. 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-2011-4595/ (Markdown: https://insights.sbomify.com/CVE-2011-4595/index.md)
```

## Sources

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

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