CVE-2025-10351
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 · uneditedSQL injection vulnerability based on the melis-cms module of the Melis platform from Melis Technology. This vulnerability allows an attacker to retrieve, create, update, and delete databases through the 'idPage' parameter in the '/melis/MelisCms/PageEdition/getTinyTemplates' endpoint.
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 confidenceA SQL injection vulnerability exists in the melis-cms module of Melis Platform where the 'idPage' parameter in the /melis/MelisCms/PageEdition/getTinyTemplates endpoint is not properly sanitized, allowing attackers to inject malicious SQL queries and potentially retrieve, create, update, or delete arbitrary database contents.
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.
-
Confirm Melis CMS is installedLook for the melis-cms module directory in your web application root (commonly under /module/MelisCms or vendor/melisplatform/melis-cms). Check composer.json or module configuration files for melis-cms presence.Affected if The melis-cms module directory or package exists in your application
-
Identify melis-cms versionCheck the version in your composer.json file under require (melisplatform/melis-cms) or in the module's composer.json or config.php file within the MelisCms module directory.Affected if You cannot determine the version or the installed version is unknown
-
Verify the vulnerable endpoint existsCheck if the file PageEdition.php or the controller handling getTinyTemplates exists in your melis-cms module under module/MelisCms/src/Controller/ and locate the getTinyTemplatesAction method.Affected if The getTinyTemplates endpoint controller exists in your installation
-
Check endpoint accessibilityReview the getTinyTemplatesAction method to determine if it requires authentication. Attempt a request to /melis/MelisCms/PageEdition/getTinyTemplates (with a test idPage value) to see if it is accessible without authentication.Affected if The endpoint is reachable without authentication or with standard user credentials
-
Inspect parameter handling for idPageOpen the getTinyTemplatesAction method in your MelisCms controller and examine how the idPage parameter is used in database queries. Look for direct string concatenation or lack of parameter binding.Affected if The idPage parameter is used in SQL queries without prepared statements or input sanitization
If melis-cms is installed and the getTinyTemplates endpoint uses the idPage parameter in raw SQL queries without prepared statements, your environment is vulnerable to CVE-2025-10351.
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 dataApply available vendor patches for the melis-cms module; if no patch exists, immediately disable or restrict access to the affected endpoint and implement proper input validation and parameterized queries for the idPage parameter.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10351 — 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-10351 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