# CVE-2023-27919: Auth bypass in NEXT ENGINE Integration Plugin (for EC-CUBE 2.0 series)

> Remote unauthenticated attackers can bypass authentication to alter system information in the NEXT ENGINE Integration Plugin for EC-CUBE.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2023
- **Updated:** 27 Jan 2025
- **Also known as:** GHSA-v4hm-xqrg-4qfp

## What is CVE-2023-27919?

CVE-2023-27919 is a medium-severity authentication bypass vulnerability in NEXT ENGINE Integration Plugin (for EC-CUBE 2.0 series), published on 10 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authentication bypass vulnerability in NEXT ENGINE Integration Plugin (for EC-CUBE 2.0 series) all versions allows a remote unauthenticated attacker to alter the information stored in the system.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-27919?

It affects 1 product.


Products: Next-Engine Next Engine Integration.

## How do I fix CVE-2023-27919?

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

## Is CVE-2023-27919 being exploited?

There is no known exploitation of CVE-2023-27919 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27919 and fix it if it is affected.

What it is: CVE-2023-27919 is a medium-severity authentication bypass vulnerability in NEXT ENGINE Integration Plugin (for EC-CUBE 2.0 series), published on 10 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-27919 in the wild and no public exploit code.

Affected product: NEXT ENGINE Integration Plugin (for EC-CUBE 2.0 series). 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-2023-27919/ (Markdown: https://insights.sbomify.com/CVE-2023-27919/index.md)
```

## Sources

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

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