CVE-2025-9147
BaseFortify
Publication date: 2025-08-19
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 |
|---|---|---|
| jasonclark | getsemantic | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9147 is a cross-site scripting (XSS) vulnerability in the getsemantic software by jasonclark. It occurs in the /index.php file where the 'view' parameter from the URL is not properly sanitized before being embedded into the HTML output. This allows an attacker to inject malicious JavaScript code that executes in the context of other users' browsers when they visit the affected page. The vulnerability arises because the 'view' parameter is directly inserted into the class attribute of the <body> tag without validation or escaping, enabling script injection. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow remote attackers to execute arbitrary JavaScript code in the browsers of users visiting the affected web page. This can lead to various impacts such as session hijacking, defacement, redirection to malicious sites, or theft of sensitive information. Exploitation requires user interaction but is considered easy, and a public proof-of-concept exploit exists. The attack can be remotely executed by manipulating the 'view' parameter in the URL, potentially compromising data integrity and user trust. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'view' parameter in the URL for improper sanitization leading to cross-site scripting (XSS). You can attempt to access the URL with a payload such as /index.php?view=\"><script>alert('xss');</script> and observe if the script executes. Additionally, you can use Google dorking with queries like 'inurl:index.php' to find potentially vulnerable instances. Network detection can involve monitoring HTTP requests for suspicious payloads targeting the 'view' parameter. Example command using curl to test the vulnerability: curl -i 'http://targetsite/index.php?view=\"><script>alert(1)</script>' and check the response for reflected script tags. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing or updating the affected product if a patched version becomes available. Since no known countermeasures or official patches are published, consider implementing input validation and output encoding on the 'view' parameter to neutralize malicious scripts. As a temporary measure, restrict or sanitize user input at the web server or application firewall level to block suspicious payloads targeting the 'view' parameter. Monitoring and blocking exploit attempts using web application firewalls (WAF) can also help reduce risk. [1]