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

By Sai Kiran Pandrala

Last verified: 2026-05-25

CVE-2026-7013 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.

What's different about CVE-2026-7013?

A security vulnerability has been detected in MaxSite CMS up to 109.3. Affected by this issue is some unknown functionality of the component mail_send Plugin. The manipulation of the argument f_subject/f_files/f_from leads to cross site scripting. The attack can be initiated remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 109.4 can resolve this issue. The identifier of the patch is 8a3946bd0a54bfb72a4d57179fcd253f2c550cd7. It is advisable to upgrade the affected component. 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-7013

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-7013 fixed by the same patch as CVE-2026-7011?

Yes. CVE-2026-7013 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-7013?

The CVSS base score is 4.8 (Medium).

Is it being exploited?

It is not currently listed in CISA KEV.

References

• Official vendor advisory: https://github.com/maxsite/cms/commit/8a3946bd0a54bfb72a4d57179fcd253f2c550cd7
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-7013
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Primary write-up: How to Fix CVE-2026-7011

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