CVE-2016-15010
Last modified
CVE-2016-15010 is a medium-severity vulnerability rated 6.1/10 on the CVSS scale. ** UNSUPPORTED WHEN ASSIGNED ** A vulnerability classified as problematic was found in University of Cambridge django-ucamlookup up to 1.9.1. Affected by this vulnerability is an unknown functionality of the component Lookup Handler. EPSS estimates a 0.55% chance of exploitation in the next 30 days.
Description
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability classified as problematic was found in University of Cambridge django-ucamlookup up to 1.9.1. Affected by this vulnerability is an unknown functionality of the component Lookup Handler. The manipulation leads to cross site scripting. The attack can be launched remotely. Upgrading to version 1.9.2 is able to address this issue. The identifier of the patch is 5e25e4765637ea4b9e0bf5fcd5e9a922abee7eb3. It is recommended to upgrade the affected component. The identifier VDB-217441 was assigned to this vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Django-Ucamlookup Project | Django-Ucamlookup | < 1.9.2 |
References
- https://github.com/uisautomation/django-ucamlookup/commit/5e25e4765637ea4b9e0bf5fcd5e9a922abee7eb3Patch, Third Party Advisory
- https://github.com/uisautomation/django-ucamlookup/releases/tag/1.9.2Third Party Advisory
- https://vuldb.com/?ctiid.217441Permissions Required, Third Party Advisory
- https://vuldb.com/?id.217441Permissions Required, Third Party Advisory
- https://github.com/uisautomation/django-ucamlookup/commit/5e25e4765637ea4b9e0bf5fcd5e9a922abee7eb3Patch, Third Party Advisory
- https://github.com/uisautomation/django-ucamlookup/releases/tag/1.9.2Third Party Advisory
- https://vuldb.com/?ctiid.217441Permissions Required, Third Party Advisory
- https://vuldb.com/?id.217441Permissions Required, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-15010?
How severe is CVE-2016-15010?
How do I fix CVE-2016-15010?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-15005CSRF tokens are generated using math/rand, which is not a cr…8.8
- CVE-2016-15006A vulnerability, which was classified as problematic, has be…5.3
- CVE-2016-15007A vulnerability was found in Centralized-Salesforce-Dev-Fram…9.8
- CVE-2016-15008A vulnerability was found in oxguy3 coebot-www and classifie…6.1
- CVE-2016-15009A vulnerability classified as problematic has been found in …8.8
- CVE-2016-1501ownCloud Server before 8.0.9 and 8.1.x before 8.1.4 allow re…
- CVE-2016-15011A vulnerability classified as problematic was found in e-Con…9.8
- CVE-2016-15012** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in…9.8
- CVE-2016-15013A vulnerability was found in ForumHulp searchresults. It has…9.8
- CVE-2016-15014A vulnerability has been found in CESNET theme-cesnet up to …5.5
- CVE-2016-15015A vulnerability, which was classified as problematic, was fo…5.3
- CVE-2016-15016A vulnerability was found in mrtnmtth joomla_mod_einsatz_sta…9.8
Are you affected by CVE-2016-15010?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
