CVE-2026-90903: joomshaper.com Easy Store extension for Joomla · Cross-Site Request Forgery (CSRF)
Affects joomshaper.com Easy Store extension for JoomlaSource CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 6 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 23 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 7 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| joomshaper.comEasy Store extension for Joomla | Affected
| Fixed in– |
AI-suggested
A fix is available that implements global CSRF token verification for all state-changing HTTP methods in the ApiController. Users should upgrade to a patched version of the Easy Store extension where this fix is applied. Since no specific patch links are provided, users should consult the vendor joomshaper.com for the official update or advisory. Until patched, administrators should be cautious of unsolicited requests and avoid interacting with untrusted content while logged into the Joomla backend.
Description
Joomla Extension - joomshaper.com - Missing CSRF Token Verification across Administrator AJAX API Endpoints in Easy Store extension 1.0.0-3.0.0 - The administrator ApiController only validated CSRF tokens inside the products() action. All other administrative AJAX endpoints (orders, coupons, media, customers, settings, tags, categories, reviews, and collections) accepted state-changing requests without checking anti-CSRF tokens. An attacker could trick a logged-in administrator into triggering unauthorized state modifications across the store backend. Resolved by implementing global CSRF verification in ApiController::execute() for all state-changing HTTP methods (POST, PUT, PATCH, DELETE) via Session::checkToken().