# CVE-2007-4881: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the u parameter in the profile script, potentially compromising user data.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6hvh-8rrq-gc2g

## What is CVE-2007-4881?

CVE-2007-4881 is a high-severity SQL injection vulnerability in n/a, published on 14 Sep 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in profile/myprofile.php in psi-labs.com social networking script (psisns), probably 1.0, allows remote attackers to execute arbitrary SQL commands via the u parameter.

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

## Which versions are affected by CVE-2007-4881?

It affects 1 product.


Products: Psi-Labs Social Networking Script Psisns.

## How do I fix CVE-2007-4881?

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

## Is CVE-2007-4881 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4881 and fix it if it is affected.

What it is: CVE-2007-4881 is a high-severity SQL injection vulnerability in n/a, published on 14 Sep 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-4881 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-2007-4881/ (Markdown: https://insights.sbomify.com/CVE-2007-4881/index.md)
```

## Sources

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

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