sales@hackhalt.com

Home / Threats / CVE-2026-124760

WordPress component - Security Vulnerability (CVE-2026-124760)

CVE-2026-124760

Vulnerability CVE-2026-124760 LOW

P-Net before 1.0.4 sets the alarm receiver state to waiting for confirmation before the data of a received alarm notification is parsed. If the parsing fails the state is not restored, and later alarm notifications of the same priority are discarded without acknowledge until the Application Relationship is released. The Application Relationship and the cyclic data exchange keep working. The attacker must be able to send an alarm notification in the context of an established Application Relationship and requires ADJACENT network access.

CVE-2026-124760

LOW CVSS 2.3 Published 2026-11-13 Updated 2026-11-13
AI Risk Low (20/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P5 Monitor
Severity Band LOW
CVSS Vector CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Affected Components 1
Reference Links 1
AI Risk Engine Low (20/100)
Exploitability Low
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-11-13 CVE published and first recorded in the threat feed.
  2. 2026-11-13 Record updated with latest vulnerability metadata.
  3. 2026-11-17 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated just now

AI enriched just now (2026-11-17 01:55 UTC)

Technical Summary

P-Net before 1.0.4 sets the alarm receiver state to waiting for confirmation before the data of a received alarm notification is parsed. If the parsing fails the state is not restored, and later alarm notifications of the same priority are discarded without acknowledge until the Application Relationship is released. The Application Relationship and the cyclic data exchange keep working. The attacker must be able to send an alarm notification in the context of an established Application Relationship and requires ADJACENT…

Potential Impact

Severity is LOW (CVSS 2.3). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Low based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 20/100 (Low, Low) with priority P5 Monitor. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

WordPress component COMPONENT · unmapped Affected: < 1.0.4 Fixed in: 1.0.4

References

What to do about this

Low priority Contained impact, or it needs privileges an attacker would rarely already hold.

Fix it

Update WordPress component to 1.0.4 or later.

That is the complete fix. Everything below is what protects you in the meantime.

No Hack Halt control meaningfully contains this one — updating is the remedy. We would rather say so than sell you something that will not help.

Start free

Not sure if you are affected?

Scan your site to see whether it runs WordPress component, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs WordPress component. Versions below 1.0.4 are vulnerable; that release and later are not.

How do I fix it?

Update WordPress component to version 1.0.4 or later. That is the complete fix.