Ihsansencan

A SQL Injection issue exists in the JSP Tickets component for Joomla! via the `ticketcode` parameter in a 'ticketlist' edit action, or the `id` parameter in a 'statuslist' (or 'prioritylist') edit action.

The issue exists due to SQL Injection in the Zh GoogleMap component for Joomla!. This occurs via the `id` parameter in specific requests, including "getPlacemarkDetails", "getPlacemarkHoverText", "getPathHoverText", or "getPathDetails" requests.

The issue exists due to SQL Injection in the Zh YandexMap component for Joomla!. This occurs via the `id` parameter in a "task=getPlacemarkDetails" request.

A SQL Injection issue exists in the JEXTN Reverse Auction component for Joomla. This issue can be exploited via a request to the `view=products&uid=` endpoint, where the `uid` parameter is vulnerable to injection.

A SQL Injection issue exists in the JEXTN Classified component for Joomla!. This issue can be exploited via a request to the "view=boutique&sid=" endpoint.

The issue exists due to SQL Injection in the JMS Music component for Joomla, which can be exploited via a search using the `keyword`, `artist`, or `username` parameter.

A SQL Injection issue exists, allowing potential exploitation via the `id` parameter in the "event.php" endpoint or the `slug` parameter in the "page.php" endpoint.

A SQL Injection issue exists in the CP Event Calendar component for Joomla!. This issue is exploitable via the `id` parameter in a "task=load" action.

A SQL Injection issue exists, allowing exploitation via the `id` parameter in API endpoints such as "/site.php", "/pagelist.php", or "/page new.php".

Name of the Vulnerable Software and Affected Versions: Flexible Poll version 1.2 Description: A SQL Injection issue exists, allowing exploitation via the `id` parameter to "mobile preview.php" or "index.php" API endpoints. Recommendations: For Flexible Poll version 1.2, avoid using the `id` parameter in the affected API endpoints until the issue is resolved. As a temporary workaround, consider restricting access to "mobile preview.php" and "index.php" to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

The issue concerns SQL Injection, which can be exploited via specific parameters in certain PHP files. The vulnerable parameters are `uid` in 'admin/userview.php', `fnum` in 'admin/viewemcamp.php', and `fn` in 'admin/viewvisitcamp.php'.

The issue is related to SQL Injection, which occurs via the `keywords` parameter to the "tutorial/" endpoint.

The issue is related to SQL Injection, which occurs via the PATH INFO to the "/detail" API endpoint. This allows for potential exploitation.

The issue concerns SQL Injection, which can be exploited via specific parameters in certain PHP files. The vulnerable parameters include `grid` in "group.php", `fid` in "profile.php", and `id` in "company details.php".

The issue is related to SQL Injection, which can be exploited via the "show-flight-result.php" endpoint, specifically through the `fl orig` or `fl dest` parameters.

The issue concerns SQL Injection, which can be exploited via specific parameters in certain PHP files. The vulnerable parameters are `f` in 'movie.php', `s` in 'tvshow.php', and `id` in 'show misc video.php'.

The issue is related to SQL Injection, which can be exploited via the `/list` API endpoint, specifically through the `gender` or `city` parameters.

The issue is related to SQL Injection, which occurs via the `category list.php` `search` parameter. This allows for potential exploitation.

The issue is related to SQL Injection, which can be exploited via the `courselist.php` `subcatid` or `popcourseid` parameters.

The issue concerns a SQL Injection problem. It affects the search-results.php file through the `Projectmain`, `proj type`, `searchtext`, `sell price`, or `maxprice` parameters.