cve.bz

CVE-2026-27553

6.5 mediumEPSS 0.6%

Medium (6.5). EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
A low-privileged remote attacker can manipulate the schema path parameter in the /index.php/diagnostics_tab/ajax_diag_table_rows endpoint using a valid user cookie allowing disclosure of all user password hashes.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-497 Exposure of Sensitive System Information to an Unauthorized Control Sphere
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-27553 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-27553?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-27553?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-27553 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Pepperl+Fuchs ICE2-8IOL1-G65L-V1Dfrom 1.0.0 before 1.7.4
Pepperl+Fuchs ICE2-8IOL-G65L-V1Dfrom 1.0.0 before 1.7.4
Pepperl+Fuchs ICE2-8IOL-K45P-RJ45from 1.0.0 before 1.7.4
Pepperl+Fuchs ICE2-8IOL-K45S-RJ45from 1.0.0 before 1.7.4
Pepperl+Fuchs ICE3-8IOL1-G65L-V1Dfrom 1.0.0 before 1.7.4
Pepperl+Fuchs ICE3-8IOL-G65L-V1Dfrom 1.0.0 before 1.7.4
Pepperl+Fuchs ICE3-8IOL-G65L-V1D-Yfrom 1.0.0 before 1.7.4
Pepperl+Fuchs ICE3-8IOL-K45P-RJ45from 1.0.0 before 1.7.4
Pepperl+Fuchs ICE3-8IOL-K45S-RJ45from 1.0.0 before 1.7.4
Phoenix Contact IOL MA8 PN DI8from 1.0.0 before 1.7.4
Phoenix Contact IOL MA8 EIP DI8from 1.0.0 before 1.7.4
Carlo Gavazzi Automation YL212CEI8M1IOfrom 1.0.0 before 1.7.4
Carlo Gavazzi Automation YN115CEI8RPIOfrom 1.0.0 before 1.7.4
Carlo Gavazzi Automation YL212CPN8M1IOfrom 1.0.0 before 1.7.4
Carlo Gavazzi Automation YN115CPN8RPIOfrom 1.0.0 before 1.7.4

Attack patterns (CAPEC)

  • CAPEC-170 Web Application Fingerprinting Likelihood: High · Severity: Low
  • CAPEC-694 System Location Discovery Likelihood: High · Severity: Very Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON