dbninja vulnerabilities and fixes

Recent CVEs affecting dbninja, with upgrade or downgrade steps. 3 tracked.

dbninja has 3 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2019-02-11. Highest priority: CVE-2019-7747 (score 57/100).

• CVE-2019-7748 MEDIUM 6.1 DOWNGRADE _includes\online.php in DbNinja 3.2.7 allows XSS via the data.php task parameter if _users/admin/tasks.php exi
• CVE-2019-7747 CRITICAL 9.6 DOWNGRADE DbNinja 3.2.7 allows session fixation via the data.php sessid parameter.
• CVE-2019-7545 MEDIUM 5.4 UPGRADE In DbNinja 3.2.7, the Add Host function of the Manage Hosts pages has a Stored Cross-site Scripting (XSS) vuln

FAQ

How do I fix dbninja 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 dbninja being exploited right now?

None of the tracked dbninja CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which dbninja CVE should I patch first?

CVE-2019-7747 currently ranks highest (57/100): DbNinja 3.2.7 allows session fixation via the data.php sessid parameter..

RSS feed for dbninja · ← Back to latest CVEs