# CVE-2018-25343: Smartshop 1 Cross-Site Request Forgery via editprofile.php

> Attackers can trick authenticated users into modifying their profiles, potentially leading to account takeover, in the Smartshop web application.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-6pf6-cr9h-j56p

## What is CVE-2018-25343?

CVE-2018-25343 is a medium-severity vulnerability in Behance Smartshop, published on 23 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2018-25343?


## How do I fix CVE-2018-25343?

No fix has been published for CVE-2018-25343 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-25343 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25343 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25343 and fix it if it is affected.

What it is: CVE-2018-25343 is a medium-severity vulnerability in Behance Smartshop, published on 23 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25343 exists.

Affected product: Behance Smartshop. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-25343/ (Markdown: https://insights.sbomify.com/CVE-2018-25343/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-25343
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-25343
- OSV: https://osv.dev/vulnerability/CVE-2018-25343

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-25343/
Summaries are generated and may contain mistakes; the official description above is the record.