PatchTheCVEjpatokal vulnerabilities
Recent CVEs affecting jpatokal products. 4 tracked.
jpatokal has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2024-08-29. Highest priority: CVE-2024-41348 (score 34/100).
- CVE-2024-41348 MEDIUM 6.1 DOWNGRADE openflights commit 5234b5b is vulnerable to Cross-Site Scripting (XSS) via php/alsearch.php
- CVE-2024-41347 MEDIUM 6.1 DOWNGRADE openflights commit 5234b5b is vulnerable to Cross-Site Scripting (XSS) via php/settings.php
- CVE-2024-41346 MEDIUM 5.4 DOWNGRADE openflights commit 5234b5b is vulnerable to Cross-Site Scripting (XSS) via php/submit.php
- CVE-2024-41345 MEDIUM 5.4 DOWNGRADE openflights commit 5234b5b is vulnerable to Cross-Site Scripting (XSS) via php/trip.php
FAQ
How do I fix jpatokal vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is jpatokal being exploited right now?
None of the tracked jpatokal CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which jpatokal CVE should I patch first?
CVE-2024-41348 currently ranks highest (34/100): openflights commit 5234b5b is vulnerable to Cross-Site Scripting (XSS) via php/alsearch.php.