Security readout for executives and security teams
Plain-English summary
PrismaWEB 1.21 for Prisma Industriale Checkweigher reportedly exposes a hardcoded password for the prismaweb account through a readable JavaScript file. If reachable by an attacker, this could undermine account security. Public exploit reference exists, but the bundle does not show active exploitation or a confirmed vendor fix.
Executive priority
Prioritize exposed operational environments first. This is an older CVE, but hardcoded credential disclosure in industrial management software can remain serious if systems are still reachable and unsupported.
Technical view
CVE-2018-9161 describes hardcoded credential disclosure: remote attackers can read user/scripts/login_par.js to discover the hardcoded prisma password for the prismaweb account in PrismaWEB 1.21. No CVSS, CWE, patch version, or official affected CPE data is provided in the source bundle.
Likely exposure
Most likely exposure is internet-facing or broadly reachable PrismaWEB 1.21 instances used with Prisma Industriale Checkweigher systems. Confirm product/version directly; the bundle lists affected metadata as n/a despite the CVE description naming PrismaWEB 1.21.
Exploitation context
A public Exploit-DB reference is listed, so proof-of-concept information appears public. CISA KEV is false in the bundle, and no cited source claims active exploitation. Treat public reachability as the key risk multiplier.
Researcher notes
Evidence is limited to the CVE description and two public references. The source bundle does not provide vendor advisory details, CVSS scoring, CWE mapping, patch status, or active exploitation evidence.
Mitigation direction
- Check Prisma Industriale guidance for a fixed release or supported mitigation.
- Remove PrismaWEB from public internet exposure.
- Restrict access to trusted management networks or VPN users.
- Review whether the prismaweb account can be disabled or changed.
- Monitor for unexpected PrismaWEB login or access activity.
Validation and detection
- Inventory PrismaWEB deployments and confirm exact version 1.21 exposure.
- Check whether user/scripts/login_par.js is reachable without authorization.
- Review access logs for requests to the referenced JavaScript file.
- Verify whether the prismaweb account exists and is active.
- Document network paths that can reach PrismaWEB management interfaces.
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.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-9161 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
- 44276CVE reference · exploit, x_refsource_EXPLOIT-DB
- https://www.zeroscience.mk/en/vulnerabilities/ZSL-2018-5453.phpCVE 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.