Readymade Video Sharing Script Project's vulnerability footprint centers on a single, focused web-based video-sharing application that exhibits a consistent pattern of web-tier input-handling and code-generation flaws. The durable signal across its disclosures is rooted in application-layer weaknesses including SQL injection, cross-site scripting, cross-site request forgery, and code injection, reflecting common vulnerabilities in server-side script execution and user-input validation. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Readymade Video Sharing Script Project over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2017-17627CRITICAL Readymade Video Sharing Script 3.2 has SQL Injection via the single-video-detail.php report_videos array parameter. | Dec 13, 2017 | 9.8 | 41 | NO | YES |
CVE-2017-17649MEDIUM Readymade Video Sharing Script 3.2 has HTML Injection via the single-video-detail.php comment parameter. | Dec 18, 2017 | 6.1 | 31 | NO | YES |
CVE-2017-17892CRITICAL Readymade Video Sharing Script has SQL Injection via the viewsubs.php chnlid parameter or the search_video.php search parameter. | Dec 27, 2017 | 9.8 | 29 | NO | NO |
CVE-2017-17891HIGH Readymade Video Sharing Script has CSRF via user-profile-edit.php. | Dec 27, 2017 | 8.8 | 26 | NO | NO |
CVE-2017-17893MEDIUM Readymade Video Sharing Script has XSS via the search_video.php search parameter, the viewsubs.php chnlid parameter, or the user-profile-edit.php fname parameter. | Dec 27, 2017 | 6.1 | 20 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Readymade Video Sharing Script Project.
Media articles that mention a CVE ID that affects a product developed by Readymade Video Sharing Script Project — matched by CVE ID, not by vendor name.