Cross-Site Scripting (XSS) in Muslim Matrimonial Script Project (CVE-2017-17985)
Summary
Cross-site scripting in Muslim Matrimonial Script Project (CVE-2017-17985). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
PHP Scripts Mall Muslim Matrimonial Script has XSS via the admin/state_view.php cou_id parameter.
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-17985 was discovered in Muslim Matrimonial Script Project.
In plain terms, it is a flaw that lets attackers sneak nasty scripts into a webpage.
Severity is Medium (CVSS 4.8/10). Exploitation requires specific conditions but can cause real harm if successful.
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 "Muslim Matrimonial Script Project CVE-2017-17985".
CVE-2017-17985 (Muslim Matrimonial Script Project). Severity: Medium / CVSSv3 4.8. Category: CWE-79.
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-17985) in Muslim Matrimonial Script Project. In plain words, it is a flaw that lets attackers sneak nasty scripts into a webpage.
Target versions of Muslim Matrimonial Script Project (see vendor advisory). If running in production, identify exposure immediately.
Severity: Medium (CVSS 4.8/10). Exploitation requires specific conditions but can cause real harm if successful.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-79)
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