Security readout for executives and security teams
Plain-English summary
PHPVibe versions before 4.21 allowed logged-in users to place script or HTML into comments. Because comments are stored, other users could later view the malicious content. The bundle does not show active exploitation, but public exploit references exist.
Executive priority
Treat this as a targeted web application risk, not an emergency based on the bundle. Prioritize remediation if PHPVibe is public-facing, business-critical, or allows broad user registration.
Technical view
CVE-2015-5399 is a stored cross-site scripting issue in PHPVibe before 4.21 via comment input. The source bundle describes remote authenticated injection of arbitrary web script or HTML. No CVSS, CWE, or detailed affected CPE data is provided.
Likely exposure
Exposure is most likely on internet-facing PHPVibe deployments before 4.21 where authenticated users can submit comments. Anonymous-only sites without user commenting are less likely exposed based on the provided description.
Exploitation context
The bundle cites Packet Storm and Exploit-DB entries, so public exploit information exists. CISA KEV status is false, and the provided sources do not state active exploitation in the wild.
Researcher notes
Evidence is sparse: no CVSS, CWE, CPE, vendor advisory, or active exploitation claim is included. Analysis should stay tied to PHPVibe before 4.21 and the authenticated stored-comment XSS vector.
Mitigation direction
- Identify all PHPVibe deployments and confirm their exact versions.
- Upgrade PHPVibe to 4.21 or later if vendor guidance confirms the fix.
- Restrict comment posting by untrusted accounts until remediation is complete.
- Review existing comments for unsafe script or HTML content.
- Monitor user sessions and admin actions for suspicious activity.
Validation and detection
- Confirm whether PHPVibe version is earlier than 4.21.
- Check whether authenticated users can submit comments.
- Review stored comments for unexpected HTML or script-like content.
- Verify upgraded instances no longer accept unsafe comment content.
- Confirm compensating controls cover public and authenticated comment paths.
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-5399 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://packetstormsecurity.com/files/132715/phpVibe-Stored-Cross-Site-Scripting.htmlCVE reference · x_refsource_MISC
- 37659CVE reference · exploit, x_refsource_EXPLOIT-DB
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.