dbcve.org
WampserverApplication

CVE-2018-1000848

MEDIUM · 6.1 CVSS v3.0 Published 2018-12-20
Fix available
A fix is available. Upgrade to 3.1.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Wampserver version prior to version 3.1.5 contains a Cross Site Scripting (XSS) vulnerability in index.php localhost page that can result in very low. This attack appear to be exploitable via payload onmouseover. This vulnerability appears to have been fixed in 3.1.5 and later.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

WampServer prior to version 3.1.5 contains a reflected Cross Site Scripting (XSS) vulnerability in the index.php localhost page. The vulnerability is exploitable via an onmouseover payload, allowing attackers to inject malicious JavaScript that executes when users hover over a crafted element.

MitigationUpgrade WampServer to version 3.1.5 or later to remediate this vulnerability. If upgrading is not immediately possible, implement input validation and output encoding on the index.php page.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WampserverApplication
Affected:< 3.1.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WampServer installation
    Look for WampServer installation directory (commonly C:\wamp64 or C:\wamp) or check Programs and Features for WampServer entry
    Affected if WampServer is installed on the system
  2. Identify installed WampServer version
    Check the WampServer version displayed in the system tray icon, or look for a version file in the installation directory, or access the localhost page and check for version information
    Affected if Installed version is lower than 3.1.5 (e.g., 3.1.4, 3.1.3, etc.)
  3. Verify localhost index.php is accessible
    Access http://localhost/ or http://localhost/index.php in a web browser
    Affected if The localhost page loads and is reachable (indicating the WampServer web service is running)

If WampServer is installed with a version below 3.1.5 and the localhost index.php page is accessible, the environment is likely affected by this XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 3.1.5 or later
Fixed in 3.1.5
Interim mitigation

Upgrade WampServer to version 3.1.5 or later to remediate this vulnerability. If upgrading is not immediately possible, implement input validation and output encoding on the index.php page.

Fix this in Wampserver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1000848 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1000848 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data