CVE-2017-5963
Last modified
CVE-2017-5963 is a vulnerability of currently unknown severity. An issue was discovered in caddy (for TYPO3) before 7.2.10. The vulnerability exists due to insufficient filtration of user-supplied data in the "paymillToken" HTTP POST parameter passed to the "caddy/Resources/Public/JavaScript/e-payment/paymill/api/php/payment.php" URL. EPSS estimates a 1.03% chance of exploitation in the next 30 days.
Description
An issue was discovered in caddy (for TYPO3) before 7.2.10. The vulnerability exists due to insufficient filtration of user-supplied data in the "paymillToken" HTTP POST parameter passed to the "caddy/Resources/Public/JavaScript/e-payment/paymill/api/php/payment.php" URL. An attacker could execute arbitrary HTML and script code in a browser in the context of the vulnerable website.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Caddy Project | Caddy | 2.1.4 | Alpha |
| Caddy Project | Caddy | 2.1.5 | Alpha |
| Caddy Project | Caddy | 2.1.6 | Alpha |
| Caddy Project | Caddy | 3.0.0 | Alpha |
| Caddy Project | Caddy | 4.0.0 | Alpha |
| Caddy Project | Caddy | 4.0.1 | Alpha |
| Caddy Project | Caddy | 4.0.2 | Alpha |
| Caddy Project | Caddy | 4.0.3 | Alpha |
| Caddy Project | Caddy | 4.0.12 | Alpha |
| Caddy Project | Caddy | 6.0.1 | Alpha |
| Caddy Project | Caddy | 6.0.2 | Alpha |
| Caddy Project | Caddy | 6.0.9 | Alpha |
| Caddy Project | Caddy | 6.0.12 | Beta |
| Caddy Project | Caddy | 6.0.14 | Beta |
| Caddy Project | Caddy | 6.1.0 | Beta |
| Caddy Project | Caddy | 6.2.1 | Beta |
| Caddy Project | Caddy | 6.3.0 | Beta |
| Caddy Project | Caddy | 6.3.1 | Beta |
| Caddy Project | Caddy | 6.3.3 | Beta |
| Caddy Project | Caddy | 7.0.0 | Beta |
| Caddy Project | Caddy | 7.1.0 | Beta |
| Caddy Project | Caddy | 7.2.7 | Beta |
References
- http://www.securityfocus.com/bid/96198Third Party Advisory, VDB Entry
- https://forge.typo3.org/issues/79325Exploit, Third Party Advisory
- http://www.securityfocus.com/bid/96198Third Party Advisory, VDB Entry
- https://forge.typo3.org/issues/79325Exploit, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-5963?
How severe is CVE-2017-5963?
How do I fix CVE-2017-5963?
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 2017
- CVE-2017-5956The vrend_draw_vbo function in virglrenderer before 0.6.0 al…
- CVE-2017-5957Stack-based buffer overflow in the vrend_decode_set_framebuf…5.5
- CVE-2017-5959CSRF token bypass in GeniXCMS before 1.0.2 could result in e…
- CVE-2017-5960An issue was discovered in Phalcon Eye through 0.4.1. The vu…
- CVE-2017-5961An issue was discovered in ionize through 1.0.8. The vulnera…
- CVE-2017-5962An issue was discovered in contexts_wurfl (for TYPO3) before…
- CVE-2017-5964An issue was discovered in Emoncms through 9.8.0. The vulner…6.1
- CVE-2017-5965The package manager in Sitecore CRM 8.1 Rev 151207 allows re…
- CVE-2017-5966Sitecore CRM 8.1 Rev 151207 allows remote authenticated admi…
- CVE-2017-5967The time subsystem in the Linux kernel through 4.9.9, when C…
- CVE-2017-5969libxml2 2.9.4, when used in recover mode, allows remote atta…
- CVE-2017-5970The ipv4_pktinfo_prepare function in net/ipv4/ip_sockglue.c …
Are you affected by CVE-2017-5963?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
