CVE-2015-9288
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 · uneditedThe Unity Web Player plugin before 4.6.6f2 and 5.x before 5.0.3f2 allows attackers to read messages or access online services via a victim's credentials
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 · moderate confidenceThe Unity Web Player plugin versions before 4.6.6f2 and 5.x before 5.0.3f2 contains an authentication bypass vulnerability that allows attackers to read messages or access online services by leveraging a victim's credentials, likely through improper session or token handling.
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< 4.6.6f2>= 5.0, < 5.0.3f2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Unity Web Player installationCheck common installation directories: On Windows, look in Program Files/Unity or the browser's plugin folders (e.g., %APPDATA%/Mozilla/Plugins, Chrome plugins folder). On Mac, check /Library/Internet Plug-Ins/ or ~/Library/Internet Plug-Ins/Affected if Unity Web Player plugin files are found on the system
-
Identify installed versionRight-click the Unity Web Player file (typically named UnityPlayer.dll or similar) and view Properties > Details to read the File Version. Alternatively, check the browser's plugin manager (navigate to about:plugins in Firefox or chrome://plugins in Chrome)Affected if The displayed version is readable and matches the affected ranges
-
Compare version against affected rangesCompare the installed version number to the vulnerable ranges: any version below 4.6.6f2, or any 5.x version below 5.0.3f2Affected if Version is < 4.6.6f2 OR (version >= 5.0 AND version < 5.0.3f2)
-
Verify plugin is enabled in browsersOpen each installed browser and check if Unity Web Player is listed as an enabled plugin (access about:plugins in Firefox or chrome://plugins in Chrome)Affected if The plugin is present AND enabled in any browser
A user is affected if Unity Web Player plugin is installed, enabled in a browser, and the version falls below 4.6.6f2 or between 5.0.0 and 5.0.3f1.
Generated from the published advisory. Verify against your own configuration.
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 data4.6.6f25.0.3f2
Upgrade Unity Web Player to version 4.6.6f2 or later, or 5.0.3f2 or later. Note that Unity Web Player has been deprecated; consider migrating to WebGL or other supported platforms.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9288 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-9288 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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