# CVE-2013-1290: Missing authorization in n/a

> Authenticated users can bypass access controls to read restricted SharePoint list items in legacy My Sites configurations.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/C:P/I:N/A:N`)
- **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:** 9 Apr 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v7rc-wwx8-7hh9

## What is CVE-2013-1290?

CVE-2013-1290 is a low-severity missing authorization vulnerability in Microsoft Sharepoint Server, published on 9 Apr 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Microsoft SharePoint Server 2013, in certain configurations involving legacy My Sites, does not properly establish default access controls for a SharePoint list, which allows remote authenticated users to bypass intended restrictions on reading list items via a direct request for a list's location, aka "Incorrect Access Rights Information Disclosure Vulnerability."

Weakness: CWE-264

## Which versions are affected by CVE-2013-1290?

It affects 1 product.


Products: Microsoft Sharepoint Server.

## How do I fix CVE-2013-1290?

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

## Is CVE-2013-1290 being exploited?

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

## Other vulnerabilities in Microsoft Sharepoint Server

- [CVE-2026-50522](https://insights.sbomify.com/CVE-2026-50522/): Microsoft SharePoint Deserialization of Untrusted Data Vulnerability (critical 9.8, exploited in the wild)
- [CVE-2026-58644](https://insights.sbomify.com/CVE-2026-58644/): Microsoft SharePoint Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2026-20963](https://insights.sbomify.com/CVE-2026-20963/): Microsoft SharePoint Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2025-53770](https://insights.sbomify.com/CVE-2025-53770/): Microsoft SharePoint Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2023-29357](https://insights.sbomify.com/CVE-2023-29357/): Microsoft SharePoint Server Privilege Escalation (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1290 and fix it if it is affected.

What it is: CVE-2013-1290 is a low-severity missing authorization vulnerability in Microsoft Sharepoint Server, published on 9 Apr 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-1290 in the wild and no public exploit code.

Affected product: Microsoft Sharepoint Server. 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-2013-1290/ (Markdown: https://insights.sbomify.com/CVE-2013-1290/index.md)
```

## Sources

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

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