Skip to main content
mySites.guru
CriticalA PHP security release fixes two CVSS 9.2 flaws, and PHP 8.1 and older get no patchWhat it means for your site

EasyStore security vulnerabilities

mySites.guru tracks 2 vulnerabilities in EasyStore (com_easystore), covering 10 CVEs. Every connected Joomla site is checked against them on each audit.

Is my site affected?

Your site is affected if it runs EasyStore in any of these ranges:

  • before 3.0.1
  • before 2.0.2
Latest safe version
3.0.1 or later. No rule we check matches that release or any newer one.
What to do
Update EasyStore to 3.0.1 or later from the vendor, then confirm the installed version on the Joomla administrator's Extensions: Manage screen.

Every EasyStore vulnerability we track

Newest first. CVSS is the score published in each CVE record, where it has one; the severity column is the rating our check uses.

CVEAffected versionsFixed inSeverityAdded
CVE-2026-90899CVSS 8.2CVE-2026-90900CVSS 5.3CVE-2026-90901CVSS 8.6CVE-2026-90902CVSS 8.6CVE-2026-90903CVSS 7.2CVE-2026-90904CVSS 8.6CVE-2026-90905CVSS 7.2before 3.0.13.0.1High2026-09-23
CVE-2026-65759CVSS 8.7CVE-2026-65760CVSS 9.2CVE-2026-65761CVSS 9.3before 2.0.22.0.2High-

What we check for

EasyStore (com_easystore) below 3.0.1 - Unauthenticated Customer Address Disclosure, Authenticated SQL Injection, CSRF and ACL Bypass

EasyStore, the JoomShaper ecommerce component for Joomla, is affected by seven flaws fixed in version 3.0.1, found and reported by mySites.guru. (1) Unauthenticated customer data disclosure: the guest checkout lookup returned a guest customer's saved shipping address (name, street address, city, postcode, country and phone number) to any anonymous visitor who supplied that customer's email address, with no login, session or ownership check. (2) Cross-site request forgery on storefront product reviews: the token check was commented out, so a page a logged-in customer visited could submit reviews in their name. Five further flaws need an administrator session and matter when an admin account is phished or shared, or when an admin is lured to a malicious page: SQL injection in media image deletion and in coupon bulk updates (ids concatenated into an IN() clause), no CSRF token check on the administrator AJAX API, an allowEdit() that always returned true and so bypassed Joomla asset permissions on record edits, and a configuration update that rewrote the site sender name and email in configuration.php with no CSRF token or access check. The flaws were reported against 3.0.0 and are present in the 2.x code as well, so every version below 3.0.1 is treated as affected. Update to EasyStore 3.0.1 or later, released 23 September 2026. The customer address disclosure is a silent read that leaves no file changes, so a clean file scan does not show a site was unaffected. CVE-2026-90899, CVE-2026-90900, CVE-2026-90901, CVE-2026-90902, CVE-2026-90903, CVE-2026-90904 and CVE-2026-90905 were published by the Joomla CNA on 23 September 2026, crediting Phil Taylor of mySites.guru.

Affected versions: < 3.0.1

Full advisory: our disclosure post

EasyStore (com_easystore) below 2.0.2 - Unauthenticated SQL Injection, Unauthenticated Order Forgery and Cross-Customer Invoice Disclosure

EasyStore, the JoomShaper ecommerce component for Joomla, is affected by three flaws in version 2.0.1 and every earlier release, found and reported by mySites.guru. (1) Unauthenticated order forgery: the checkout repayment task built the order from client-supplied JSON including the payment status and wrote it to the database with no login, no CSRF token, no ownership check and no contact with any payment gateway, so an anonymous request could mark any order paid (goods released without payment) and rewrite arbitrary fields on any order id. CWE-862 and CWE-639, CVSS 4.0 8.7 High. (2) Unauthenticated SQL injection: the product list sort parameter passed its direction into the query ORDER BY clause without an allow-list, giving an anonymous visitor a read of any table in the database including Joomla user accounts, password hashes and the site secret. CWE-89, CVSS 4.0 8.7 High. (3) Cross-customer order and invoice disclosure: the order detail page and printable invoice checked only that a user was logged in, never that the order belonged to them, and order ids are sequential, so any registered customer could read every other customer name, email address, billing and shipping address, phone number and purchase history. CWE-639, CVSS 4.0 7.1 High. Update to EasyStore 2.0.2 or later, released 23 July 2026. JoomShaper shipped 2.0.2 with no security advisory and described the three fixes as routine changelog lines. A web application firewall filtering SQL may block the injection but does nothing about the order forgery or the invoice exposure, so it is mitigation rather than a fix. Both the invoice exposure and the SQL injection are silent reads that leave no file changes, so a clean file scan does not indicate a site was unaffected. A CVE has been applied for through the Joomla CNA and is not yet assigned. Assigned CVE-2026-65759, CVE-2026-65760, CVE-2026-65761 (all affect <= 2.0.1, fixed 2.0.2).

Affected versions: < 2.0.2

Full advisory: our disclosure post

Timeline

  1. 23 July 2026CVE-2026-65759 record published
  2. 23 July 2026CVE-2026-65760 record published
  3. 23 July 2026CVE-2026-65761 record published
  4. 23 July 2026We published: Exposed Customer Invoices, Order Forgery and SQL Injection in EasyStore for Joomla found by mySites.guru
  5. 23 September 2026Check added for CVE-2026-90899, CVE-2026-90900, CVE-2026-90901, CVE-2026-90902, CVE-2026-90903, CVE-2026-90904 and CVE-2026-90905 (before 3.0.1)
  6. 23 September 2026CVE-2026-90899 record published
  7. 23 September 2026CVE-2026-90900 record published
  8. 23 September 2026CVE-2026-90901 record published
  9. 23 September 2026CVE-2026-90902 record published
  10. 23 September 2026CVE-2026-90903 record published
  11. 23 September 2026CVE-2026-90904 record published
  12. 23 September 2026CVE-2026-90905 record published
  13. 23 September 2026We published: EasyStore 3.0.1 Fixes Seven Security Flaws mySites.guru Found in 3.0.0 on Release Day

What we have written about EasyStore

References

Each CVE page above links its official cve.org record and its NVD entry.

EasyStore vulnerability questions

Which versions of EasyStore are vulnerable?
mySites.guru tracks 2 vulnerabilities in EasyStore (com_easystore). A site is affected if its installed version is in any of these ranges: before 3.0.1; before 2.0.2.
What is the latest safe version of EasyStore?
3.0.1. Every vulnerability tracked here is fixed by 3.0.1, and no rule we check matches that release or any later one.
How do I check which version of EasyStore my Joomla site runs?
The installed version is listed on the Joomla administrator's Extensions: Manage screen; search it for com_easystore. mySites.guru reads the installed version on every audit of a connected site and checks it against these rules.

Running EasyStore on a site you manage?

A free audit tells you which of your Joomla and WordPress sites run an affected version, which are out of date, and which have not been backed up. No card required. If a site is already compromised, fix.mysites.guru is a single fixed fee per incident, usually resolved the same day.

This check is part of the mySites.guru Joomla vulnerability scanner, which reads every installed extension's version on each audit. Browse the rest of the Joomla vulnerability database.

CVE identifiers: CVE-2026-90899, CVE-2026-90900, CVE-2026-90901, CVE-2026-90902, CVE-2026-90903, CVE-2026-90904, CVE-2026-90905, CVE-2026-65759, CVE-2026-65760, CVE-2026-65761. Rules current as of 24 October 2026.