Security readout for executives and security teams
Plain-English summary
MaxSite CMS versions before V106 had a reflected XSS flaw in product/page/* routes. An attacker could cause malicious script to appear in a victim's browser if the victim follows a crafted link. The sources do not show confirmed exploitation or detailed business impact.
Executive priority
Treat as a normal-priority web application remediation unless the affected CMS hosts sensitive workflows or authenticated user sessions. Prioritize patching public-facing instances because XSS can support phishing, session abuse, or user impersonation depending on site context.
Technical view
CVE-2021-35265 is a reflected cross-site scripting vulnerability in MaxSite CMS before V106. The vulnerable surface is described as product/page/*, where remote attackers can inject arbitrary web script into a page. Public evidence is limited to the CVE record, GitHub issue, and upstream commit.
Likely exposure
Exposure is likely limited to organizations running MaxSite CMS before V106, especially internet-facing sites with product/page/* routes enabled. The source bundle does not identify affected CPEs, hosting patterns, or downstream packaged products.
Exploitation context
The CVE is public and references a GitHub issue and commit. CISA KEV status is false, and the supplied sources do not claim active exploitation. Reflected XSS typically depends on getting a victim to open a crafted URL or page.
Researcher notes
Evidence is sparse: no CVSS vector, CWE mapping, CPEs, or exploit telemetry are provided. The best-supported scope is MaxSite CMS before V106 and product/page/* routes. Avoid expanding affected products beyond the CVE description and upstream repository evidence.
Mitigation direction
- Upgrade MaxSite CMS to V106 or later if applicable.
- Apply the upstream fix referenced by the vendor commit.
- Review vendor guidance before making custom code changes.
- Limit public exposure of affected routes if upgrade is delayed.
- Add temporary monitoring for suspicious product/page/* requests.
Validation and detection
- Inventory MaxSite CMS installations and confirm deployed versions.
- Check whether product/page/* routes are internet-accessible.
- Verify the upstream fix commit is present in deployed code.
- Confirm output encoding on affected pages after remediation.
- Review logs for unusual requests targeting product/page/*.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-35265 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/maxsite/cms/issues/414#issue-726249183CVE reference · x_refsource_MISC
- https://github.com/maxsite/cms/commit/6b0ab1de9f3d471485d1347e800a9ce43fedbf1aCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.