CVE-2025-6301
BaseFortify
Publication date: 2025-06-20
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| anujk305 | notice_board_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-6301 is a Stored Cross-Site Scripting (XSS) vulnerability in PHPGurukul Notice Board System version 1.0. It occurs in the admin panel's Add Notice feature where the Title and Description input fields do not properly sanitize or encode HTML content. This allows an attacker to inject malicious JavaScript code that gets stored and later executed when viewing notices, potentially affecting authenticated admin users or others who view the notices. [1, 2]
How can this vulnerability impact me? :
This vulnerability can lead to arbitrary JavaScript execution in the context of authenticated users, especially admins. Potential impacts include admin session hijacking, phishing attacks, and full account compromise. Since the malicious script executes when notices are viewed, it can be exploited remotely after authentication, posing a high risk to the integrity and security of the system. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable admin page /admin/manage-notices.php and testing the input fields for Title and Description for improper sanitization of HTML or JavaScript content. One method is to use Google dorking with the query "inurl:admin/manage-notices.php" to identify potentially vulnerable targets. Additionally, manual testing can be done by submitting payloads such as `<img src=x onerror=alert(0)>` in the Title or Description fields and observing if the script executes when viewing notices. Network detection could involve monitoring HTTP requests to /admin/manage-notices.php for suspicious payloads containing script tags or event handlers. [2, 1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing user inputs on the server side using PHP functions like `htmlspecialchars($input, ENT_QUOTES, 'UTF-8')` to encode HTML entities, applying HTML filtering libraries such as HTMLPurifier, enforcing strong Content Security Policy (CSP) headers to restrict script execution, enabling output encoding or framework-based XSS protections, and validating input length and allowed characters before storage. If possible, restrict access to the admin panel and consider replacing the vulnerable product with an alternative. Monitoring and applying patches or updates when available is also recommended. [1]