Security readout for executives and security teams
Plain-English summary
Mautic used PHP mt_rand to create session tokens. That generator is not suitable for security tokens, so a logged-in attacker could potentially predict or enumerate tokens tied to other accounts. The published severity is low, with limited availability impact and no confirmed active exploitation in the provided sources.
Executive priority
Handle during normal vulnerability remediation unless the Mautic instance is highly exposed or business-critical. The issue is real cryptographic weakness, but public severity is low and the provided sources do not show active exploitation.
Technical view
CVE-2021-27913 is CWE-327 in Mautic session-token generation. The issue is the use of mt_rand, a non-cryptographic pseudorandom function, for tokens. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L with score 3.5. Affected versions are reported as prior to 3.3.4 and prior to 4.0.0.
Likely exposure
Exposure is limited to organizations running affected Mautic versions before 3.3.4 or before 4.0.0, based on the CVE source bundle. Internet-facing Mautic instances are more reachable, but the CVSS vector requires attacker privileges and user interaction.
Exploitation context
The sources describe a theoretical attack path against weak session-token generation, not confirmed exploitation. CISA KEV status is false in the bundle. Do not treat this as known exploited without additional vendor, incident, or KEV evidence.
Researcher notes
The evidence supports weak token generation through mt_rand, but does not include exploit maturity, patch diff details, or operational indicators. Validate exposure by version first. Avoid extrapolating this to other Mautic token types unless confirmed by the advisory or code review.
Mitigation direction
- Upgrade affected Mautic deployments to 3.3.4, 4.0.0, or later supported releases.
- Review the Mautic GitHub advisory for exact version and upgrade guidance.
- Invalidate existing sessions after upgrading if vendor guidance recommends it.
- Limit Mautic administrative access to trusted users and networks where feasible.
Validation and detection
- Inventory all Mautic deployments and record exact running versions.
- Compare versions against the affected ranges in the CVE and advisory.
- Confirm upgraded instances report 3.3.4, 4.0.0, or later supported versions.
- Check session-management configuration against current Mautic vendor guidance.
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.
CWE-327: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-27913 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
- Low
- CVSS
- 3.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L2.11.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.5LowVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/mautic/mautic/security/advisories/GHSA-x7g2-wrrp-r6h3CVE 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.
Use of a Broken or Risky Cryptographic Algorithm
Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.