Cyber Resilience

CVE-2026-48943

Joomlaworks K2 ≤ 2.26

Published
25 June 2026
Modified
28 June 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0018 8th percentile
Risk Priority 49 floored blend · peak EPSS

Summary

CVE-2026-48943 is a medium-severity Improperly Controlled Modification of Dynamically-Determined Object Attributes (CWE-915) vulnerability in Joomlaworks K2. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

K2 ≤ 2.24 contains a mass-assignment defect in the K2 system user plugin `plg_user_k2`. A Registered Joomla user, by including the field `K2UserForm=1` in a standard `com_users` `profile.save` POST, can write arbitrary values into the `notes`, `image`, and `plugins` columns…

more

of their own row in the `#__k2_users` table — none of which are exposed by the K2 frontend profile-edit form.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1098 Account Manipulation Persistence
Adversaries may manipulate accounts to maintain and/or elevate access to victim systems.
T1098.001 Additional Cloud Credentials Persistence
Adversaries may add adversary-controlled credentials to a cloud account to maintain persistent access to victim accounts and instances within the environment.
T1098.003 Additional Cloud Roles Persistence
An adversary may add additional roles or permissions to an adversary-controlled cloud account to maintain persistent access to a tenant.
T1098.004 SSH Authorized Keys Persistence
Adversaries may modify the SSH <code>authorized_keys</code> file to maintain persistence on a victim host.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-48941Same product: Joomlaworks K2
CVE-2026-48944Same product: Joomlaworks K2
CVE-2026-48942Same product: Joomlaworks K2
CVE-2026-48945Same product: Joomlaworks K2
CVE-2026-48946Same product: Joomlaworks K2
CVE-2026-48940Same product: Joomlaworks K2
CVE-2026-12535Shared CWE-915
CVE-2026-55809Shared CWE-915
CVE-2026-58477Shared CWE-915
CVE-2026-21695Shared CWE-915

Affected Assets

joomlaworks
k2
≤ 2.26

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Enforces authorizations so that only permitted attributes may be modified on an object.

Limits the set of modifiable attributes a subject is authorized to touch.

Validates incoming attribute names and values so that only explicitly allowed fields are accepted for update.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require allow-listing of mutable object attributes and input validation to block mass-assignment flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards explicitly forbid unsafe dynamic attribute assignment and require property allow-lists.

finds

Security testing can detect mass-assignment flaws but does not itself prevent them at runtime.

prevents

Secure development lifecycle requires input validation and object-property whitelisting that directly mitigates mass-assignment risks.

prevents

Application security requirements include explicit rules for allowable object attributes and safe deserialization.

prevents

Secure architecture principles mandate strict control over dynamic object modification and attribute binding.

prevents

Information access restriction limits who can modify objects but does not address which attributes may be changed.

References