Security readout for executives and security teams
Plain-English summary
Pixelimity 1.0 has a stored cross-site scripting issue in the portfolio admin title field. If malicious script is saved there, it may run later in a browser viewing the affected content. Sources do not provide CVSS, confirmed fixes, or active exploitation evidence.
Executive priority
Treat as a targeted web application risk, not a broad emergency. Prioritize if Pixelimity 1.0 is internet-facing or accepts content from non-admin users.
Technical view
The CVE describes persistent XSS in `admin/portfolio.php` through the `data[title]` parameter, demonstrated with an SVG event attribute. The available record does not list CWE, CPEs, fixed versions, or detailed affected configurations beyond Pixelimity 1.0.
Likely exposure
Exposure appears limited to Pixelimity 1.0 deployments, especially where untrusted or lower-privileged users can reach portfolio administration or influence portfolio title content.
Exploitation context
The issue is publicly documented in a GitHub issue and CVE records. The source bundle says KEV is false, and no cited source confirms active exploitation in the wild.
Researcher notes
Evidence is sparse: the CVE confirms stored XSS and one affected parameter, but lacks CVSS, CPE mapping, fixed versions, and exploitation telemetry. Validate against actual deployed code before scoping remediation.
Mitigation direction
- Check Pixelimity vendor or repository guidance for a fixed release or patch.
- Restrict access to portfolio administration to trusted administrators only.
- Sanitize existing portfolio title content for unexpected markup or scripts.
- Apply output encoding and input validation if maintaining a local fork.
- Consider retiring Pixelimity 1.0 if no maintained fix is available.
Validation and detection
- Inventory public sites and internal apps for Pixelimity 1.0 usage.
- Review `admin/portfolio.php` handling of `data[title]` in maintained copies.
- Inspect portfolio title records for unexpected HTML, SVG, or script-like content.
- Confirm in a safe test environment that saved titles render as text, not executable markup.
- Verify administrative access controls around portfolio editing.
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-2018-19919 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/pixelimity/pixelimity/issues/19CVE 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.