# CVE-2014-125132: Blogroll Fun WordPress Plugin < 0.8.5 Reflected XSS via blogroll.php


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-vcg9-96r7-4fvx

## What is CVE-2014-125132?

CVE-2014-125132 is a medium-severity vulnerability in Jason Newman Blogroll Fun, published on 20 Oct 2026. 

### Official description

Blogroll Fun plugin for WordPress before 0.8.5 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the 'k' parameter in blogroll.php. Attackers can craft GET requests to /wp-content/plugins/blogroll-fun/blogroll.php with malicious 'k' values that are echoed unsanitized, executing JavaScript in victims' browsers. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.

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

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


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

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

## Is CVE-2014-125132 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-125132 is a medium-severity vulnerability in Jason Newman Blogroll Fun, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2014-125132 in the wild and no public exploit code.

Affected product: Jason Newman Blogroll Fun. 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-125132/ (Markdown: https://insights.sbomify.com/CVE-2014-125132/index.md)
```

## Sources

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

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