CVE-2025-10352
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVulnerability in the melis-core module of Melis Technology's Melis Platform, which, if exploited, allows an unauthenticated attacker to create an administrator account via a request to '/melis/MelisCore/ToolUser/addNewUser'.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe melis-core module in Melis Platform contains an authentication bypass vulnerability in the addNewUser endpoint (/melis/MelisCore/ToolUser/addNewUser). An unauthenticated remote attacker can send a crafted request to this endpoint to create a new administrator-level account, gaining full administrative access to the platform without any credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify melis-core module versionLocate the melis-core module in your Melis Platform installation and check its version. This is typically found in a composer.json file, a module.xml file, or a version.php file within the melis-core module directory.Affected if The installed version of melis-core falls within the affected range (verify against official Melis Platform security advisories for CVE-2025-10352).
-
Confirm addNewUser endpoint existsCheck if the ToolUser controller file exists in the melis-core module at a path similar to /module/MelisCore/src/Controller/ToolUserController.php and contains an addNewUser or addnewuser method.Affected if The endpoint method exists in the codebase and is publicly accessible without authentication checks.
-
Test endpoint accessibilityAttempt a GET or POST request to /melis/MelicCore/ToolUser/addNewUser (or the actual endpoint path) from an unauthenticated context (no session cookie, no API token).Affected if The endpoint responds without redirecting to a login page or returning an authentication error, indicating it is accessible without credentials.
-
Review authentication middlewareExamine the module's routing configuration (often in module.config.php) to determine if any authentication middleware or guard is applied to the ToolUser controller or the addNewUser route.Affected if No authentication middleware is assigned to the addNewUser route, or the middleware is improperly configured to allow unauthenticated access.
-
Audit existing administrator accountsQuery the user database table (commonly users or similar naming in the Melis database) for administrator accounts that were not created by known administrators or that appear suspicious.Affected if Unexpected administrator-level accounts exist in the system that were not created through legitimate administrative workflows.
You are affected if the melis-core module is installed with the vulnerable endpoint exposed and accessible without authentication, or if unauthorized admin accounts are found in the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authentication and role-based authorization checks on the addNewUser endpoint to ensure only authenticated users with administrative privileges can create new user accounts. Additionally, consider implementing CSRF protection and input validation for all user creation operations.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10352 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data