LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25100: The Mojolicious module before 7.66 for Perl may leak cookies in certain situations related to multiple simi...

The Mojolicious module before 7.66 for Perl may leak cookies in certain situations related to multiple similar cookies for the same domain. This affects Mojo::UserAgent::CookieJar.

MediumCVSS 5.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Mojolicious versions before 7.66 can mishandle cookies when several similar cookies exist for the same domain. That can cause the wrong cookie behavior and possible cookie leakage from applications using its Perl user-agent cookie jar. Business risk is usually moderate and dependency-driven, not broad infrastructure compromise.

Executive priority

Prioritize remediation during the next dependency maintenance window, sooner for systems handling authentication cookies or sensitive cross-domain workflows. There is no supplied evidence of active exploitation, but cookie boundary issues can affect trust decisions in connected services.

Technical view

The issue affects Mojo::UserAgent::CookieJar in the Perl Mojolicious module before 7.66. The CVE describes leakage related to multiple similar cookies for one domain. The CVSS 3.1 vector is network-exploitable with low complexity, no privileges, and no user interaction, but only low integrity impact is scored.

Likely exposure

Exposure is likely in Perl applications, jobs, or integrations that use Mojolicious before 7.66 and rely on Mojo::UserAgent cookie persistence across domains. Systems not using Mojolicious, or using 7.66 or newer, are not indicated as affected by the supplied sources.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, or public weaponization. Practical exploitation depends on application-specific cookie flows involving multiple similar cookies for the same domain. Treat it as a dependency hygiene and session-boundary risk unless local evidence shows sensitive cookie handling.

Researcher notes

Evidence is limited to the CVE record and Mojolicious issue, PR, commit, and change log references. The affected CPE data is not populated in the bundle. Do not broaden scope beyond Mojolicious before 7.66 without confirming downstream packaging or vendored copies.

Mitigation direction

  • Upgrade Mojolicious to version 7.66 or later.
  • Review the Mojolicious change log and linked fix before release.
  • Rebuild and redeploy affected Perl services after dependency update.
  • Regression test cookie handling for same-domain similar-cookie cases.
  • If upgrading is delayed, check Mojolicious project guidance for supported workarounds.

Validation and detection

  • Inventory deployed Perl applications using Mojolicious.
  • Check lockfiles and runtime package versions for Mojolicious below 7.66.
  • Identify code using Mojo::UserAgent::CookieJar or persistent user-agent cookies.
  • Run existing unit and integration tests after the dependency update.
  • Confirm no production image still ships the vulnerable module version.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-400: 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 lookup
cve · low confidence lookup

CVE-2018-25100 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2018-25100Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-400

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.