Joomla JoomOCShop 1.0 contains a cross-site request forgery vulnerability that allows attackers to perform unauthorized actions on behalf of authenticated users. Attackers can craft malicious HTML forms targeting account endpoints like /joomoc2/?route=account/edit and to modify user information or reset passwords without user consent.
Security readout for executives and security teams
Plain-English summary
CVE-2018-25337 affects JoomOCShop 1.0, a Joomla e-commerce extension. It is a cross-site request forgery issue that could let an attacker cause an authenticated user to make unwanted account changes, such as profile updates or password reset actions. Business risk is mainly account integrity disruption on sites still using this old extension version.
Executive priority
Treat as a targeted cleanup item, not an emergency, unless JoomOCShop 1.0 supports business-critical commerce workflows. Prioritize identifying whether the extension exists in your environment, then update, disable, or replace it based on vendor guidance and operational need.
Technical view
The vulnerability is CWE-352 in Joomlaextensions JoomOCShop 1.0. The CVE description identifies CSRF against account endpoints including /joomoc2/?route=account/edit, enabling unauthorized actions as an authenticated user. CVSS v4.0 is 5.3, with low attack complexity and limited integrity impact. Sources do not identify a vendor patch or fixed version.
Likely exposure
Exposure is limited to Joomla sites with the JoomOCShop extension version 1.0 installed and reachable. Organizations not using this extension are not affected based on the provided sources. Risk is higher where authenticated customer or administrator sessions are common and the component is internet-facing.
Exploitation context
A public ExploitDB entry is referenced, so technical details have been publicly available. However, the CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. CSRF generally depends on a victim being authenticated and induced to interact with attacker-controlled content.
Researcher notes
Evidence supports a CSRF issue in JoomOCShop 1.0 with a public ExploitDB reference. The source bundle does not provide patch details, affected versions beyond 1.0, or proof of active exploitation. Avoid assuming impact on other Joomla extensions or later JoomOCShop versions without vendor confirmation.
Mitigation direction
Inventory Joomla sites for the JoomOCShop extension and confirm installed version.
If JoomOCShop 1.0 is present, review vendor or extension directory guidance for updates.
Disable or remove the extension if it is unused or unsupported.
Apply compensating controls for authenticated account changes, such as re-authentication where feasible.
Monitor account profile and password-related changes for suspicious activity.
Validation and detection
Check Joomla extension inventory for JoomOCShop version 1.0.
Review web routes for JoomOCShop account edit functionality exposure.
Verify whether vendor documentation lists a fixed release or replacement guidance.
Review logs for unusual account edit or password reset activity.
Confirm CSRF protections exist on sensitive account-changing requests.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.