vulnerability / NVI-00006117 / Revision 3
Use of a Broken or Risky Cryptographic Algorithm
OSV carries this publisher advisory for mautic/core, mautic/core. This is an aggregated source copy; consult the original publisher and compare update dates.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
3.5 LOW (2.0)
nvd@nist.gov severity; no combined Null risk score.
3.5 LOW (3.1)
security@mautic.org severity; no combined Null risk score.
3.5 LOW (3.1)
nvd@nist.gov severity; no combined Null risk score.
0.458%
FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.39754. Missing scores are unknown.
As of · FIRST EPSS
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
mautic/core
source listedECOSYSTEM: introduced 0; fixed 3.3.4
## ✍️ Description The function mt_rand is used to generate session tokens, this function is cryptographically flawed due to its nature being one pseudorandomness, an attacker can take advantage of the cryptographically insecure nature of this function to enumerate session tokens for accounts that are not under his/her control ## 🕵️♂️ Proof of Concept Numerous examples and attack implementations can be found in this paper . If you're looking for a practical tool that can crack your mt_rand implementation's seed value, see this project and run the following commands in a console with php5 and OpenWall's tool installed: `root$ php -r 'mt_srand(13333337); echo mt_rand( ), "\n";'` After that, copy the output (1863134308) and execute the following commands: `root$ gcc php_mt_seed.c -o php_mt_seedroot$ ./php_mt_seed 1863134308` After waiting ~1 minute you should have a few possible seeds corresponding to their PHP versions, next to your installed PHP version you should see something akin to: seed = 0x00cb7359 = 13333337 (PHP 7.1.0+) Hey, that's your seed! ## 💥 Impact An attacker could takeover accounts at random by enumerating and using access tokens. ## 📝 References - https://
mautic/core
source listedECOSYSTEM: introduced 4.0.0-alpha1; fixed 4.0.0
## ✍️ Description The function mt_rand is used to generate session tokens, this function is cryptographically flawed due to its nature being one pseudorandomness, an attacker can take advantage of the cryptographically insecure nature of this function to enumerate session tokens for accounts that are not under his/her control ## 🕵️♂️ Proof of Concept Numerous examples and attack implementations can be found in this paper . If you're looking for a practical tool that can crack your mt_rand implementation's seed value, see this project and run the following commands in a console with php5 and OpenWall's tool installed: `root$ php -r 'mt_srand(13333337); echo mt_rand( ), "\n";'` After that, copy the output (1863134308) and execute the following commands: `root$ gcc php_mt_seed.c -o php_mt_seedroot$ ./php_mt_seed 1863134308` After waiting ~1 minute you should have a few possible seeds corresponding to their PHP versions, next to your installed PHP version you should see something akin to: seed = 0x00cb7359 = 13333337 (PHP 7.1.0+) Hey, that's your seed! ## 💥 Impact An attacker could takeover accounts at random by enumerating and using access tokens. ## 📝 References - https://
03 / Response
What to do next
- vendor patch
The original advisory lists fixed boundaries 3.3.4 for mautic/core. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- vendor patch
The original advisory lists fixed boundaries 4.0.0 for mautic/core. Confirm the publisher’s latest guidance.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database via OSV
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. FIRST EPSS
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
- NVD lastModified does not establish freshness of every associated CPE record.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-x7g2-wrrp-r6h3 ↗
GitHub Advisory Database via OSV · vendor advisory
Observed . GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.
- CVE-2021-27913 ↗
NIST National Vulnerability Database · official catalog
Observed . This product uses data from the NVD API but is not endorsed or certified by the NVD.
- CVE-2021-27913 ↗
FIRST EPSS · official catalog
Observed . FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 3 ·
Source facts changed; compare the preserved prior revision.
- Revision 2 ·
Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.