Security readout for executives and security teams
Plain-English summary
prettyPhoto before 3.1.6 contains a cross-site scripting issue in its JavaScript lightbox code. Affected websites could expose visitors to attacker-controlled script execution in their browsers. The public record is sparse, with no CVSS score or detailed affected product list provided.
Executive priority
Prioritize remediation where prettyPhoto is used on public-facing or authenticated customer-facing pages. The absence of active-exploitation evidence lowers urgency, but XSS in client-facing code still warrants scheduled remediation and validation.
Technical view
CVE-2015-9478 describes XSS in js/jquery.prettyPhoto.js before version 3.1.6. The supplied sources identify the upstream release and issue, but do not provide CWE, CVSS, exploit details, or a CPE mapping. Treat exposure as any deployed, bundled, forked, or minified prettyPhoto copy older than 3.1.6.
Likely exposure
Exposure is most likely in public websites, themes, plugins, or legacy applications that bundle prettyPhoto directly rather than through tracked package management. Static JavaScript copies can persist unnoticed in build output, CDN paths, or vendor folders.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Because this is XSS, successful abuse would generally depend on how a site uses the library and whether attacker-controlled input reaches the vulnerable behavior.
Researcher notes
The CVE metadata is minimal: no CVSS, CWE, CPE, or detailed exploit conditions are supplied. Analysis should focus on confirming actual library presence and version, then reviewing the upstream 3.1.6 release and issue for implementation-specific context.
Mitigation direction
- Inventory all deployed copies of jquery.prettyPhoto.js.
- Upgrade prettyPhoto to version 3.1.6 or later.
- Replace bundled, forked, or minified vulnerable copies.
- Check upstream release and issue notes before production rollout.
- Add XSS regression coverage for affected UI flows.
Validation and detection
- Confirm no deployed prettyPhoto copy is older than 3.1.6.
- Search source, build output, CDN assets, and vendor folders.
- Verify gallery or lightbox flows after upgrade.
- Run browser-side security regression tests for XSS handling.
- Document any remaining legacy exposure and compensating controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2015-9478 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/scaron/prettyphoto/releases/tag/3.1.6CVE reference · x_refsource_MISC
- https://github.com/scaron/prettyphoto/issues/149CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.