CVE-2025-60313

6.1 MEDIUM

📋 TL;DR

CVE-2025-60313 is a Cross-Site Scripting (XSS) vulnerability in Sourcecodester Link Status Checker 1.0 that allows remote attackers to inject malicious scripts via the URL input field. This affects all users running the vulnerable version of this PHP web application. Attackers can execute arbitrary JavaScript in victims' browsers when they view the manipulated link status results.

💻 Affected Systems

Products:
  • Sourcecodester Link Status Checker
Versions: 1.0
Operating Systems: Any OS running PHP web server
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations of version 1.0. The vulnerability is in the web interface's URL input field.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal session cookies, redirect users to malicious sites, perform actions on behalf of authenticated users, or deliver malware payloads through the vulnerable application.

🟠

Likely Case

Session hijacking, credential theft, or defacement of the application interface through injected content.

🟢

If Mitigated

Limited impact with proper input validation and output encoding, potentially only affecting the specific user viewing manipulated results.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

XSS vulnerabilities typically have low exploitation complexity. No public proof-of-concept was found in the provided references.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None found

Restart Required: No

Instructions:

1. Check Sourcecodester website for updated version
2. Replace vulnerable files with patched versions
3. Implement proper input validation and output encoding

🔧 Temporary Workarounds

Input Validation Filter

PHP

Add server-side validation to sanitize URL inputs before processing

Implement PHP filter_var() with FILTER_VALIDATE_URL or custom regex validation

Output Encoding

PHP

Encode all user-controlled output before rendering in HTML

Use htmlspecialchars() or htmlentities() when displaying URL results

🧯 If You Can't Patch

  • Implement a Web Application Firewall (WAF) with XSS protection rules
  • Disable or restrict access to the vulnerable application until patching is possible

🔍 How to Verify

Check if Vulnerable:

Test by entering a basic XSS payload like <script>alert('XSS')</script> in the URL input field and check if it executes

Check Version:

Check the application's version file or documentation, typically in readme.txt or version.php

Verify Fix Applied:

Test with same XSS payloads and verify they are properly sanitized or encoded in output

📡 Detection & Monitoring

Log Indicators:

  • Unusual long URL parameters containing script tags or JavaScript code
  • Multiple failed input validation attempts

Network Indicators:

  • HTTP requests with suspicious script tags in URL parameters
  • Unexpected JavaScript in application responses

SIEM Query:

web.url:*script* OR web.url:*javascript* AND dest.app:"Link Status Checker"

🔗 References

📤 Share & Export