Security readout for executives and security teams
Plain-English summary
Kalles Addons for WordPress is reported vulnerable through version 1.0.6. An unauthenticated remote attacker may submit unsafe serialized data, potentially compromising site data, content, or availability. The 9.8 CVSS score indicates urgent risk, but the supplied evidence does not confirm exploitation or identify a fixed release.
Executive priority
Treat as an urgent exposure-assessment and remediation item for any public WordPress estate. Immediate attention is justified by unauthenticated remote reachability and a 9.8 score. Escalate confirmed installations through incident-response channels if suspicious changes appear, while recognizing that active exploitation and a fixed version are not established by this bundle.
Technical view
CVE-2026-73389 is classified as CWE-502: deserialization of untrusted data, resulting in unauthenticated PHP object injection. The CVSS 3.1 vector indicates network access, low complexity, no privileges, and no user interaction, with high confidentiality, integrity, and availability impact. The bundle contains conflicting affected-status metadata, so version applicability should be verified.
Likely exposure
Potentially exposed systems are internet-reachable WordPress sites running Kalles Addons version 1.0.6 or earlier. However, the structured affected record lists versions as “n/a” and default status as “unaffected,” conflicting with the title and description. Confirm installed versions and vendor applicability before final scoping.
Exploitation context
The source bundle does not establish active exploitation, and this CVE is not listed as KEV in the supplied data. It describes unauthenticated, network-reachable exploitation conditions, but provides no verified attack observations, exploit availability, prerequisites beyond the affected plugin, or evidence of weaponization.
Researcher notes
The principal evidence gap is contradictory applicability metadata: narrative fields say Kalles Addons through 1.0.6 is affected, while the structured affected entry says “n/a” and defaults to unaffected. No vulnerable code path, affected endpoint, gadget chain, patch commit, fixed version, or exploitation telemetry is supplied. Avoid asserting code execution without additional evidence.
Mitigation direction
- Identify all WordPress sites using Kalles Addons and record installed versions.
- Check The4 and Patchstack guidance for a confirmed fixed release or mitigation.
- Prioritize restricting or disabling the plugin where business operations permit.
- Apply the vendor-confirmed update promptly when its fixed version is established.
- Preserve relevant web and application logs before making changes.
Validation and detection
- Verify plugin presence and version across production, staging, and dormant WordPress sites.
- Confirm affected-version status against current The4 or Patchstack guidance.
- Review logs for unusual unauthenticated requests and unexplained WordPress changes.
- Check administrator accounts, plugin files, themes, content, and scheduled tasks for unauthorized changes.
- After remediation, confirm the vulnerable plugin version is absent or disabled.
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.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-73389 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/kalles-addons/vulnerability/wordpress-kalles-addons-plugin-1-0-6-php-object-injection-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
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.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.