CVE-2026-7014
Cross-Site Scripting in MaxSite CMS down_count Plugin
Publication date: 2026-04-26
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 |
|---|---|---|
| maxsite | maxsite_cms | to 109.4 (exc) |
| maxsite | down_count_plugin | to 1.4 (exc) |
| maxsite | down_count_plugin | 1.4 |
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?
This vulnerability is a cross-site scripting (XSS) flaw found in MaxSite CMS up to version 109.3, specifically in the down_count Plugin component. It occurs due to improper handling of the arguments f_file and f_prefix, which allows an attacker to inject malicious scripts. The attack can be initiated remotely by manipulating these inputs.
The vendor classifies this issue as a "Self-XSS" and has addressed it by applying proper input filtering using the htmlspecialchars() function in version 109.4, which prevents incorrect data display and mitigates the vulnerability.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute malicious scripts in the context of the affected website, potentially leading to unauthorized actions or data manipulation within the user's browser session.
However, the CVSS scores indicate a low severity impact (BaseScore 2.4 in v3.1), with no direct impact on confidentiality or availability, but a low impact on integrity. The attack requires user interaction and high privileges, which limits the risk.
Upgrading to version 109.4 of MaxSite CMS resolves this issue by properly sanitizing inputs.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves cross-site scripting (XSS) caused by manipulation of the f_file/f_prefix arguments in the down_count plugin of MaxSite CMS up to version 109.3.
Detection can involve checking for unusual or suspicious input values in these parameters that might include HTML or JavaScript code.
Since the exploit is remote and involves web requests, monitoring HTTP requests to the affected plugin endpoints for suspicious payloads is advisable.
Specific commands are not provided in the available resources or context.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade MaxSite CMS and the down_count plugin to version 109.4 or later, where the vulnerability has been fixed by applying proper input sanitization using the htmlspecialchars() function.
This update prevents the XSS vulnerability by escaping user-supplied data in the affected plugin.
Until the upgrade can be applied, consider restricting access to the vulnerable plugin endpoints or implementing web application firewall (WAF) rules to block suspicious input patterns targeting f_file/f_prefix parameters.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how this vulnerability directly affects compliance with common standards and regulations such as GDPR or HIPAA.