What is the CVSS score of CVE-2025-61603?

CVE-2025-61603 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of PHP are affected by CVE-2025-61603?

Organizations using WeGIA face critical risk from CVE-2025-61603, a SQL injection vulnerability rated CVSS 9.8.. A patch is available.

Is there a public PoC exploit available for CVE-2025-61603?

Yes, a public proof-of-concept exploit is available for CVE-2025-61603. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2025-61603?

Within 24 hours: Identify all affected systems and apply vendor patches immediately. Validate that input sanitization is in place for all user-controlled parameters.

PHP CVE-2025-61603

EUVD-2025-33217 CRITICAL

SQL Injection (CWE-89)

2025-10-02 security-advisories@github.com

SQLi PHP Wegia

9.8

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

EUVD ID Assigned

Mar 13, 2026 - 19:12 euvd

EUVD-2025-33217

Analysis Generated

Mar 13, 2026 - 19:12 vuln.today

PoC Detected

Oct 07, 2025 - 15:43 vuln.today

Public exploit code

Patch released

Oct 07, 2025 - 15:43 nvd

Patch available

CVE Published

Oct 02, 2025 - 20:15 nvd

CRITICAL 9.8

DescriptionGitHub Advisory

WeGIA is a Web manager for charitable institutions. Versions 3.4.12 and below include an SQL Injection vulnerability which was identified in the /controle/control.php endpoint, specifically in the descricao parameter. This vulnerability allows attackers to execute arbitrary SQL commands, compromising the confidentiality, integrity, and availability of the database. This issue is fixed in version 3.5.0.