Swift vulnerabilities

5 vulnerabilities

Known vulnerabilities in Swift products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 5 products.

Products

5
7.5CVE-2018-16386swiftalliance_web_platform
EPSS score
1.14%
An issue was discovered in SWIFT Alliance Web Platform 7.1.23. A log injection (and an arbitrary log filename) can be achieved via the PATH_INFO to swp/login/EJBRemoteService/, related to com.swift.ejbgwt.j2ee.client.EjBlnvocationException error log information containing null@java:comp/env/ error messages.
6.4CVE-2025-5258swiftconference scheduler+1
EPSS score
0.29%
The Conference Scheduler plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘className’ parameter in all versions up to, and including, 2.5.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
7.5CVE-2020-9840applenioextras+1
EPSS score
1.02%
In SwiftNIO Extras before 1.4.1, a logic issue was addressed with improved restrictions.
7.5CVE-2020-9861appleswift+1
EPSS score
1.45%
A stack overflow issue existed in Swift for Linux. The issue was addressed with improved input validation for dealing with deeply nested malicious JSON input.
9.3CVE-2026-103922@capacitorandroid+8
EPSS score
0.21%
Capacitor is a cross-platform native runtime for web applications. From 6.0.0 until 6.2.2, 7.6.9, 8.3.5, 8.4.3, and 8.5.1, the Android and iOS WebView navigation guard validates a target URL's host and scheme but not its path, allowing a victim who activates an untrusted link to navigate a frame to /_capacitor_http_interceptor_. The native proxy can fetch an attacker-selected URL and return the response as a document at the application's own origin, allowing script in that response to access same-origin storage, cookies, and registered Capacitor plugin capabilities. Applications remain affected when CapacitorHttp is disabled because affected releases serve the proxy path regardless of that setting. This issue is fixed in versions 6.2.2, 7.6.9, 8.3.5, 8.4.3, and 8.5.1.