How widely exploitable is this vulnerability?

It is remotely exploitable wherever the `details` endpoint is exposed over the network. Any attacker who can send HTTP requests to this endpoint and control the `ID` parameter may attempt SQL injection.

Does an attacker need authenticated access to exploit it?

The description does not indicate an authentication requirement, so exploitation may be possible as an unauthenticated user if the endpoint is publicly accessible. If deployments restrict access or require login, those controls can raise the bar but do not eliminate the underlying flaw.

What is the safest general fix pattern for this issue?

Refactor the affected code to use parameterized queries or an ORM so the `ID` value is always bound as a parameter, combined with strict validation of the expected `ID` format. Avoid any direct string concatenation or interpolation when building SQL queries.

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Song-Li cross_browser details Endpoint

CVE-2026-5577

Published:

Apr 5, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-94

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

Remote Code Execution by authenticated users via malicious file upload

May 10, 2026

CWE-94

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Remote Code Execution by Authenticated Users

May 10, 2026

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-74;CWE-89

Impact:

Data Exposure and Data Integrity Compromise via SQL Injection

Severity:

HIGH RISK

(7.3)

CVSS Version:

3.1

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-74;CWE-89

Impact:

Data Exposure and Data Integrity Compromise via SQL Injection

Severity:

HIGH RISK

(7.3)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

SQL Injection (CWE-89) in Song-Li cross_browser details Endpoint

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal