Skip to main content
VulnerabilityPublished

CVE-2026-90904: joomshaper.com Easy Store extension for Joomla · Improper Access Control

Affects joomshaper.com Easy Store extension for JoomlaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High.

Data as of 6 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
joomshaper.comEasy Store extension for JoomlaAffected
  • =1.0.0-3.0.0
Fixed in–

AI-suggested

A fix is available that replaces the hardcoded true return in allowEdit() with proper ACL authorization checks using AccessControl::create()->canEdit(). Users should update the Easy Store extension to a version that includes this fix. Until patched, restrict backend user access to trusted administrators only.

Description

Joomla Extension - joomshaper.com - Broken Access Control (ACL Bypass) in ApiController Record Editing in Easy Store extension 1.0.0-3.0.0 - The allowEdit() method in ApiController.php hardcoded return true;, bypassing Joomla component-level and asset-level ACL permission checks. Any authenticated backend user could edit any EasyStore record, regardless of specific ACL permission grants. Resolved by replacing the hardcoded boolean with proper ACL authorization checks via AccessControl::create()->canEdit()`.

References

Community reviews

Loading reviews…