# CVE-2015-6510: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via multiple parameters in pfSense, potentially leading to session hijacking or privilege escalation.

- **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:** 18 Aug 2015
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-23pf-vqh8-2w2c

## What is CVE-2015-6510?

CVE-2015-6510 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Aug 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

Multiple cross-site scripting (XSS) vulnerabilities in pfSense before 2.2.3 allow remote attackers to inject arbitrary web script or HTML via the (1) srctrack, (2) use_mfs_tmp_size, or (3) use_mfs_var_size parameter to system_advanced_misc.php; the (4) port, (5) snaplen, or (6) count parameter to diag_packet_capture.php; the (7) pppoe_resethour, (8) pppoe_resetminute, (9) wpa_group_rekey, or (10) wpa_gmk_rekey parameter to interfaces.php; the (11) pppoe_resethour or (12) pppoe_resetminute parameter to interfaces_ppps_edit.php; the (13) member[] parameter to interfaces_qinq_edit.php; the (14) port or (15) retry parameter to load_balancer_pool_edit.php; the (16) pkgrepourl parameter to pkg_mgr_settings.php; the (17) zone parameter to services_captiveportal.php; the port parameter to (18) services_dnsmasq.php or (19) services_unbound.php; the (20) cache_max_ttl or (21) cache_min_ttl parameter to services_unbound_advanced.php; the (22) sshport parameter to system_advanced_admin.php; the (23) id, (24) tunable, (25) descr, or (26) value parameter to system_advanced_sysctl.php; the (27) firmwareurl, (28) repositoryurl, or (29) branch parameter to system_firmware_settings.php; the (30) pfsyncpeerip, (31) synchronizetoip, (32) username, or (33) passwordfld parameter to system_hasync.php; the (34) maxmss parameter to vpn_ipsec_settings.php; the (35) ntp_server1, (36) ntp_server2, (37) wins_server1, or (38) wins_server2 parameter to vpn_openvpn_csc.php; or unspecified parameters to (39) load_balancer_relay_action.php, (40) load_balancer_relay_action_edit.php, (41) load_balancer_relay_protocol.php, or (42) load_balancer_relay_protocol_edit.php.

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

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

It affects 1 product.


Products: Netgate Pfsense.

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

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

## Is CVE-2015-6510 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16915](https://insights.sbomify.com/CVE-2019-16915/): Path traversal in n/a (critical 9.8)
- [CVE-2020-21487](https://insights.sbomify.com/CVE-2020-21487/): Cross-site scripting in n/a (critical 9.6)
- [CVE-2024-46538](https://insights.sbomify.com/CVE-2024-46538/): Cross-site scripting in n/a (critical 9.3)
- [CVE-2023-48123](https://insights.sbomify.com/CVE-2023-48123/): Command injection in n/a (high 8.8)
- [CVE-2023-42326](https://insights.sbomify.com/CVE-2023-42326/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-6510 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Aug 2015. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-6510 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-2015-6510/ (Markdown: https://insights.sbomify.com/CVE-2015-6510/index.md)
```

## Sources

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

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