Cross-Site Request Forgery (CSRF) in Readymade Video Sharing Script Project (CVE-2017-17891)
Summary
Vulnerability in Readymade Video Sharing Script Project (CVE-2017-17891). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
Readymade Video Sharing Script has CSRF via user-profile-edit.php.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2017-17891 was discovered in Readymade Video Sharing Script Project.
In plain terms, it is a CSRF flaw that lets attackers act as the victim.
Severity is High (CVSS 8.8/10). If exploited, attackers can leak data or disrupt key functionality.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "Readymade Video Sharing Script Project CVE-2017-17891".
CVE-2017-17891 (Readymade Video Sharing Script Project). Severity: High / CVSSv3 8.8. Category: CWE-352.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2017-17891) in Readymade Video Sharing Script Project. In plain words, it is a CSRF flaw that lets attackers act as the victim.
Target versions of Readymade Video Sharing Script Project (see vendor advisory). If running in production, identify exposure immediately.
Severity: High (CVSS 8.8/10). If exploited, attackers can leak data or disrupt key functionality.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-352)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
References
- exploit github.com