SQL injection vulnerability in page.php in Vlinks 1.0.3 and 1.1.6 allows remote attackers to execute arbitrary SQL commands via the id para…

published 2011-09-09 15y ago modified 2026-06-16 4mo ago also EUVD-2009-5046

cvss: 7.5; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits: 1; Exploit-DB

SQL injection vulnerability in page.php in Vlinks 1.0.3 and 1.1.6 allows remote attackers to execute arbitrary SQL commands via the id parameter.

Is CVE-2009-5091 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

Timeline

2009-02-13 First public exploit (EDB-8050)
2011-09-09 Published

Exploit prediction

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

Exploits and checks

EDB-8050 Vlinks 1.1.6 - 'id' SQL Injection webapps, 2009-02-13
securityfocus.com http://www.securityfocus.com/bid/33766 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

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

References

exploit-db.com /exploits/8050
exploit
securityfocus.com /bid/33766
vdb-entry, exploit
secunia.com /advisories/33931
third-party-advisory, vendor-advisory
exchange.xforce.ibmcloud.com /vulnerabilities/48729
vdb-entry

Sources

CVE List CVE-2009-5091
NVD CVE-2009-5091

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.