How severe is CVE-2018-25080?

CVE-2018-25080 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2018-25080?

CVE-2018-25080 affects the following packages: mobiledetect/mobiledetectlib (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2018-25080?

Update mobiledetect/mobiledetectlib to 2.8.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-25080 is resolved across your whole dependency graph.

How do I detect CVE-2018-25080 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mobiledetect/mobiledetectlib, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-25080 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2018-25080 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2018-25080, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-25080?

CVE-2018-25080 has an EPSS (Exploit Prediction Scoring System) score of 2.7%, placing it in the 86th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-25080?

CVE-2018-25080 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2018-25080 published, and has it been updated?

CVE-2018-25080 was published on February 4, 2023 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2018-25080 — mobiledetectlib

MEDIUMFix: serbanghita/Mobile-Detect@31818a4

CVE-2018-25080 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in mobiledetect/mobiledetectlib. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for mobiledetect/mobiledetectlib — see the affected versions and patch details below.

Cross-site Scripting in MobileDetect

Also known asGHSA-r77c-qv68-j3pp

Published

Feb 4, 2023

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘mobiledetect/mobiledetectlib

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability, which was classified as problematic, has been found in MobileDetect 2.8.31. This issue affects the function initLayoutType of the file examples/session_example.php of the component Example. The manipulation of the argument $_SERVER['PHP_SELF'] leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.8.32 is able to address this issue. The identifier of the patch is 31818a441b095bdc4838602dbb17b8377d1e5cce. It is recommended to upgrade the affected component. The identifier VDB-220061 was assigned to this vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`mobiledetect/mobiledetectlib`	all versions	2.8.32`composer require mobiledetect/mobiledetectlib:^2.8.32`

Affected Products

1 product · 1 configurations

Application

mobiledetectmobiledetect

1 version

2.8.31

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52454webappsphp

MobileDetect 2.8.31 - Cross-Site Scripting (XSS)

by CodeSecLab · Dec 3, 2025

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mobiledetect/mobiledetectlib, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mobiledetect/mobiledetectlib to 2.8.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-25080 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-25080 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Feb 4, 2023

First exploit

Dec 3, 2025

Last updated

Oct 20, 2026

Identifiers

CVE-2018-25080

GHSA-r77c-qv68-j3pp

References

Advisorygithub.com · 2.8.32 Advisorynvd.nist.gov · CVE 2018 25080 Fixgithub.com · 31818a441b095bdc4838602dbb17b8377d1e5cce Fixgithub.com Reportvuldb.com Reportvuldb.com Webgithub.com · CVE 2018 25080.md Packagegithub.com · Mobile Detect

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs with CWE-79 are rated as high or higher (top: critical).

CVE-2026-113787CVE-2026-44267CVE-2026-96632CVE-2026-9086CVE-2026-118246CVE-2026-118251CVE-2026-118253CVE-2026-116797Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026