CVE-2018-25343: Smartshop 1 Cross-Site Request Forgery via editprofile.php
Smartshop 1 contains a cross-site request forgery vulnerability that allows attackers to modify user profiles by tricking authenticated users into submitting malicious requests. Attackers can craft HTML forms targeting editprofile.php with hidden fields for email and password parameters that execute automatically when visited by an authenticated admin user.
Security readout for executives and security teams
Plain-English summary
Smartshop 1.0 has a cross-site request forgery issue in profile editing. If an authenticated privileged user is tricked into visiting a malicious page, profile details such as email or password-related fields could be changed. The source bundle does not name a vendor patch or active exploitation.
Executive priority
Handle as a targeted web application risk, not an emergency without exploitation evidence. Prioritize if Smartshop supports customer transactions, admin accounts, or public storefront operations.
Technical view
The issue is CWE-352 in Smartshop 1.0, affecting editprofile.php profile update handling. The provided CVSS 4.0 score is 5.3, with low integrity impact across vulnerable and subsequent systems. Public exploit information is referenced, but KEV status is false and no active exploitation evidence is provided.
Likely exposure
Exposure is likely limited to organizations still running Smartshop 1.0, especially internet-facing e-commerce deployments with authenticated profile or admin workflows. The source bundle does not provide CPEs, deployment prevalence, or fixed-version data.
Exploitation context
A public ExploitDB reference exists, so defenders should assume technical details are available. The bundle does not show known ransomware use, mass exploitation, KEV listing, or confirmed exploitation in the wild.
Researcher notes
Evidence is sufficient for the affected product, version, weakness class, and vulnerable endpoint. Evidence is incomplete for maintained status, patch availability, affected CPEs, prevalence, and exploitation in the wild.
Mitigation direction
Identify whether Smartshop 1.0 is deployed anywhere.
Check vendor or project guidance for a supported fix.
Replace or retire unsupported Smartshop deployments if no fix exists.
Restrict administrative/profile access while remediation is assessed.
Review recent profile changes for unauthorized email or password updates.
Validation and detection
Inventory public websites and internal apps for Smartshop 1.0.
Review application routes for editprofile.php exposure.
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.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.