Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 4.8

How to Fix CVE-2026-7014: CMS (Bundle Sibling)

By Sai Kiran Pandrala

Last verified: 2026-05-25

CVE-2026-7014 is a sibling vulnerability in the same vendor advisory as CVE-2026-7011. Applying the patched build named in the primary write-up closes this CVE as well.

⚡ At a glance
SeverityCVSS 4.8 - Medium
Actively exploited?Not currently in CISA KEV
AffectedSame as the bundle - see CVE-2026-7011
Fixed inSame patched build as CVE-2026-7011 (109.4)
Type (CWE)CWE-79: Cross Site Scripting

What's different about CVE-2026-7014?

A flaw has been found in MaxSite CMS up to 109.3. This vulnerability affects unknown code of the component down_count Plugin. This manipulation of the argument f_file/f_prefix causes cross site scripting. The attack may be initiated remotely. The exploit has been published and may be used. Upgrading to version 109.4 is able to resolve this issue. Patch name: 8a3946bd0a54bfb72a4d57179fcd253f2c550cd7. The affected component should be upgraded. The vendor was informed early about this issue. They classify it as a "Self-XSS".

The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.

How to fix CVE-2026-7014

Apply the patched build per the primary write-up: How to Fix CVE-2026-7011.

The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.

Frequently asked questions

Is CVE-2026-7014 fixed by the same patch as CVE-2026-7011?

Yes. CVE-2026-7014 ships in the same vendor advisory as CVE-2026-7011. Applying the patched build named in the primary write-up closes both.

What is the CVSS score for CVE-2026-7014?

The CVSS base score is 4.8 (Medium).

Is it being exploited?

It is not currently listed in CISA KEV.

References


*Part of the CMS bundle. Full procedure at CVE-2026-7011.*