CVE-2013-1290 json
Microsoft SharePoint Server 2013, in certain configurations involving legacy My Sites, does not properly establish default access controls…
published 13y ago modified 4mo ago also EUVD-2013-1330
- cvss
- 3.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 17.0%
- EPSS 17.0% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
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."
Is CVE-2013-1290 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
16.99% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2013/ms13-030
vendor-advisory
-
us-cert.gov
/ncas/alerts/TA13-100A
third-party-advisory, us-government-resource
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15758
vdb-entry, signature
Sources
- CVE List CVE-2013-1290
- NVD CVE-2013-1290
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.