CVE-2026-10301: itsourcecode Fees Management System index.php cross site scripting

Published Jun 1, 2026
·
Updated

A vulnerability was detected in itsourcecode Fees Management System 1.0. The affected element is an unknown function of the file index.php. Performing a manipulation of the argument page results in cross site scripting. The attack may be initiated remotely. The exploit is now public and may be used.

Affected Software

1 affected component
itsourcecode itsourcecode Fees Management System=1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Implement strict server-side input validation for the 'page' argument (prefer whitelist of allowed values) and apply proper output encoding/escaping before rendering to prevent cross-site scripting.

    itsourcecode Fees Management System (index.php) page parameter handling = validate and HTML-encode output
  2. Compensating control

    Deploy a Web Application Firewall or input filtering to block known XSS payloads targeting the 'page' parameter and restrict/limit external access to the application until a permanent fix is implemented.

Event History

Jun 1, 2026
CVE Published
via MITRE·11:15 PM
Data Sourced
via MITRE·11:15 PM
DescriptionSeverityWeakness
Jun 2, 2026
Data Sourced
via NVD·12:16 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-10301?

CVE-2026-10301 has a severity rating of medium with a score of 4.3.

2

What is the nature of the vulnerability in CVE-2026-10301?

CVE-2026-10301 involves a cross-site scripting (XSS) vulnerability in the index.php file of itsourcecode Fees Management System.

3

How can CVE-2026-10301 be exploited?

CVE-2026-10301 can be exploited by manipulating the argument 'page' in the index.php file, allowing remote attacks.

4

How do I fix CVE-2026-10301?

To fix CVE-2026-10301, ensure that input validation and output encoding are properly implemented to mitigate XSS risks.

5

Is CVE-2026-10301 currently being exploited in the wild?

Yes, the exploit for CVE-2026-10301 has been made public and may be used actively by attackers.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203