Skip to main content
VulnerabilityPublished

CVE-2026-90900: 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 5.3 Medium.

Data as of 6 Nov 2026, 23:24 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N/VI:L/VA:N/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 7 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 and has been implemented by the vendor. The vulnerability was resolved by enforcing anti-CSRF token checks in the ProductController and ensuring the review form includes the session token in the submission payload. Users should update to a patched version of the Easy Store extension that includes these fixes. No additional mitigation steps are required beyond applying the official fix.

Description

Joomla Extension - joomshaper.com - Missing CSRF Token Verification in Storefront Product Review Submission in Easy Store extension 1.0.0-3.0.0 - The product review submission endpoint (index.php?option=com_easystore&task=product.addReview) accepted submissions without verifying an anti-CSRF token (the check had been commented out in code). An attacker could trick a logged-in user into posting unauthorized reviews or submitting review spam via cross-site requests. Resolved by enforcing Session::checkToken('request') / Session::checkToken('post') in ProductController, injecting HTMLHelper::_('form.token') into the review form template, and appending the session token to the submission payload in review-form.js.

References

Community reviews

Loading reviews…