# CVE-2015-6522: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the size parameter in the WP Symposium plugin, potentially compromising database integrity.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-49vj-fjgr-9vmw

## What is CVE-2015-6522?

CVE-2015-6522 is a high-severity SQL injection vulnerability in n/a, published on 19 Aug 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in the WP Symposium plugin before 15.8 for WordPress allows remote attackers to execute arbitrary SQL commands via the size parameter to get_album_item.php.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Wpsymposium Wp Symposium.

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

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

## Is CVE-2015-6522 being exploited?

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

Public exploit code:

- WordPress Plugin WP Symposium 15.1 - 'get_album_item.php' SQL Injection (exploitdb)
- WordPress Symposium Plugin SQL Injection (metasploit)

## Other vulnerabilities in n/a

- [CVE-2015-3325](https://insights.sbomify.com/CVE-2015-3325/): SQL injection in n/a (high 7.5)
- [CVE-2011-5051](https://insights.sbomify.com/CVE-2011-5051/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-6522 is a high-severity SQL injection vulnerability in n/a, published on 19 Aug 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-6522 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-2015-6522/ (Markdown: https://insights.sbomify.com/CVE-2015-6522/index.md)
```

## Sources

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

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