Skip to main content
VulnerabilityPublished

CVE-2026-90905: joomshaper.com Easy Store extension for Joomla · Cross-Site Request Forgery (CSRF)

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

0
Compare

Not known to be exploited · CVSS 7.2 High.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 4.0 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% 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: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 enforces anti-CSRF token validation and administrative permission checks before updating mail configuration settings. Users should upgrade to a patched version of the Easy Store extension that includes these security controls. Until patched, administrators should avoid visiting untrusted sites while logged into Joomla to reduce risk.

Description

Joomla Extension - joomshaper.com - Missing CSRF and Access Control on Site Configuration Update in Easy Store extension 1.0.0-3.0.0 - The endpoint administrator/index.php?option=com_easystore&task=appconfig.updateConfiguration updated core Joomla mail configuration (fromname, mailfrom) in configuration.php without verifying anti-CSRF tokens or checking for administrative permissions (canAdmin). A malicious site could silently modify the site's sender name and email address via forged requests from an admin's browser. Resolved by enforcing Session::checkToken('request') / Session::checkToken('post') and adding explicit administrative authorization verification via AccessControl::create()->canAdmin().

References

Community reviews

Loading reviews…