Ignite Global Support Home Start a conversation Sign in
Start a conversation
  1. DNN Corp. Customer Support
  2. DNN Articles
  3. Articles

Evoq vs Community DNN Platform v9.13.10: Version Alignment and Security Fix Coverage

Overview

If you are waiting for Evoq to “match” the community DNN Platform v9.13.10 release tag (a security hotfix release), be aware that Evoq and the community DNN Platform do not always share the same base version number. Evoq 9.13.10 is confirmed (per its release notes) to be based on DNN Platform 9.13.9, while still including targeted security fixes, so version-number parity is not the best indicator of security coverage.

No committed schedule/date was provided for an Evoq build that is “based on” community DNN Platform v9.13.10.

Key Information

  • No runtime error is involved. This is an information request about release alignment and security-fix coverage.
  • Base version numbers may differ. Evoq and the community DNN Platform do not always align on the same underlying “based on” platform version.
  • Confirmed via release notes: Evoq 9.13.10 is based on DNN Platform 9.13.9.
  • Confirmed security fixes included in Evoq 9.13.10 (as documented in the Evoq 9.13.10 release notes) include:
    • Multiple XSS mitigations
    • IP filtering hardening at login
    • Mitigations to prevent SMB/NTLM hash leakage
    • CKEditor upload hardening
  • The community DNN Platform v9.13.10 release is described as a security-only hotfix for customers who cannot yet upgrade to DNN v10.
  • Engineering context referenced Evoq 9.13.10 as security fixes backported from DNN 10 (internal tracking item), reinforcing that included fixes are the right comparison point—not base-version parity.

Customer Impact

Recommended approach: validate whether the specific security mitigations you require are present in your Evoq version by comparing release-note fix lists, not by expecting Evoq to use the same community base version tag.

  1. Identify your installed Evoq version using your normal admin/system information view (or your standard version-reporting method).
  2. Review Evoq release notes for your target version (for example, “Evoq 9.13.10 Release Notes”): evoq_release_notes_url.
  3. Compare security-fix coverage (not base version numbers):
    • If you track a specific vulnerability/CVE, match your security requirements to the fix descriptions listed in the Evoq release notes.
    • If needed, map the community hotfix items listed for DNN Platform v9.13.10 to Evoq’s fix list: community_release_url.
  4. Upgrade to the latest available Evoq patch that explicitly contains the fixes you need.

Expected outcome: you can confirm security coverage based on documented fixes in the Evoq release notes, even when the Evoq “based on” community platform version number does not match the community tag.

Note: This guidance does not include a committed roadmap date for when Evoq will be “based on” community DNN Platform v9.13.10.

Frequently Asked Questions

1. How do I know if this applies to me?
This applies if you are asking “when will Evoq match community DNN Platform v9.13.10?” and you notice Evoq release notes indicate a different “based on” platform version (for example, Evoq 9.13.10 based on 9.13.9). There is no error message involved—this is a version-alignment and security-coverage question.
2. Does Evoq 9.13.10 include security fixes even though it’s based on DNN Platform 9.13.9?
Yes. Evoq 9.13.10 release notes document targeted security fixes (including multiple XSS mitigations, IP filtering hardening, SMB/NTLM hash leakage hardening, and CKEditor upload hardening) even though the base platform version is 9.13.9.
3. Is community DNN Platform v9.13.10 required to address the vulnerabilities?
The community DNN Platform v9.13.10 release is described as a security-only hotfix for customers who cannot yet upgrade to DNN v10. For Evoq customers, the recommended verification method is to confirm the needed mitigations are included in the Evoq release notes for your version.
4. What should I verify after upgrading Evoq for security fixes?
(1) Confirm the installed Evoq version matches the intended target version, and (2) verify the specific security fixes you care about are listed in that version’s release notes: evoq_release_notes_url. If you track a specific CVE, validate coverage by matching the fix description to your security requirement list.
5. What if I need an exact date for when Evoq will “match” a community version number?
Request an official schedule through your standard support channel. This article clarifies versioning expectations and how to verify included security fixes, but it does not include a committed future release date.
Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted

Comments