evandro-machado Trabalho-Web2 ClienteDAO.java sql injection

published 2023-01-17 3y ago modified 2026-06-17 4mo ago also EUVD-2015-1074

cvss: 5.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits: 0; none known

A vulnerability was found in evandro-machado Trabalho-Web2. It has been classified as critical. This affects an unknown part of the file src/java/br/com/magazine/dao/ClienteDAO.java. The manipulation leads to sql injection. The patch is named f59ac954625d0a4f6d34f069a2e26686a7a20aeb. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-218427.

Patch / fix

fixed in 1 links 1

trabalho-web2_project trabalho-web2 2015-06-09

github.com/evandro-machado/Trabalho-Web2@f59ac95 commit

Is CVE-2015-10061 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.5	CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
CNA	3.0	5.5	CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
CNA	2.0	5.2	AV:A/AC:L/Au:S/C:P/I:P/A:P
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

evandro-machado Trabalho-Web2

Classification

Weakness

CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

github.com /evandro-machado/Trabalho-Web2/commit/f59ac954625d0a4f6d34f069a2e26686a7a20aeb
patch, third-party-advisory
vuldb.com /?id.218427
vdb-entry, technical-description, third-party-advisory
vuldb.com /?ctiid.218427
signature, permissions-required, third-party-advisory, vdb-entry

Sources

CVE List CVE-2015-10061
NVD CVE-2015-10061

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.