Security readout for executives and security teams
Plain-English summary
MetInfo 6.0 has a cross-site scripting issue in save.php. An attacker could place script or HTML through the webname or weburl fields, potentially affecting users who view the resulting page. The source bundle does not provide severity scoring, exploit-in-the-wild evidence, or a confirmed fixed version.
Executive priority
Treat this as a targeted web application hygiene issue. Prioritize systems exposed to untrusted users or administrators, but do not escalate as emergency without evidence of active exploitation or broader impact.
Technical view
CVE-2018-9928 describes XSS in MetInfo 6.0 save.php via the webname and weburl parameters. The bundle does not identify CVSS, CWE, CPEs, authentication requirements, data persistence, or vendor remediation details.
Likely exposure
Exposure is likely limited to organizations running MetInfo 6.0 with reachable save.php functionality. The bundle does not confirm whether exploitation requires an authenticated role or a specific configuration.
Exploitation context
The KEV flag is false, and no supplied source states active exploitation. A public GitHub reference exists, indicating public technical awareness, but the bundle does not establish real-world exploitation.
Researcher notes
Key gaps are authentication context, stored versus reflected behavior, affected configuration scope, CVSS, and fixed version. Avoid assuming exploitability beyond the documented webname and weburl parameter injection in MetInfo 6.0.
Mitigation direction
- Inventory internet-facing and internal MetInfo installations for version 6.0.
- Check MetInfo vendor guidance for fixed versions or supported upgrade paths.
- Restrict access to save.php where business operations allow.
- Ensure webname and weburl output is safely encoded before rendering.
- Review WAF rules as a temporary control, not a substitute for patching.
Validation and detection
- Confirm whether MetInfo 6.0 is deployed in production or staging.
- Review save.php handling of webname and weburl for output encoding.
- Use safe, non-executing markers in authorized testing to verify injection behavior.
- Check logs for unusual changes to site name or URL fields.
- Verify remediation by confirming unsafe HTML is rendered inert.
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-9928 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/Sm1L3ing/xss-in-metinfo/blob/master/README.mdCVE 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.