# CVE-2010-3781: Privilege escalation in n/a

> Remote authenticated users can escalate privileges via crafted script code in SECURITY DEFINER functions within the PL/php add-on for PostgreSQL.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/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:** 6 Oct 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5vr6-jmmj-7xx7

## What is CVE-2010-3781?

CVE-2010-3781 is a medium-severity vulnerability in n/a, published on 6 Oct 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The PL/php add-on 1.4 and earlier for PostgreSQL does not properly protect script execution by a different SQL user identity within the same session, which allows remote authenticated users to gain privileges via crafted script code in a SECURITY DEFINER function, a related issue to CVE-2010-3433.

Weakness: CWE-264

## Which versions are affected by CVE-2010-3781?

It affects 1 product.


Products: Alvaro Herrera Pl\/Php.

## How do I fix CVE-2010-3781?

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

## Is CVE-2010-3781 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3781 and fix it if it is affected.

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

## Sources

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

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