dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-3325

CRITICAL · 10.0 CVSS v4.0 Published 2026-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
SQL injection (SQLi) in MegaCMS v12.0.0, specifically in the “id_territorio” parameter of the “/web_comunications/cms/get_provincias” endpoint. The vulnerability arises from inadequate validation and sanitisation of user input. Specifically, via a POST request, the “id_territorio” parameter, used immediately after the registration form is submitted, could be manipulated by an unauthenticated attacker to execute arbitrary SQL queries.

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 confidence

A critical SQL injection vulnerability exists in MegaCMS v12.0.0 where the 'id_territorio' parameter in the /web_comunications/cms/get_provincias endpoint fails to validate and sanitize user input. An unauthenticated attacker can inject arbitrary SQL queries via a crafted POST request, potentially gaining full database access including read/write capabilities.

MitigationImplement parameterized queries (prepared statements) for all database operations involving user input, and add robust input validation with allowlist filtering for the id_territorio parameter. Consider deploying a WAF as an interim protective control.

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:H/SI:H/SA:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MegaCMS installation
    Check for MegaCMS files on the web server, typically in the document root. Look for directories or files containing 'MegaCMS' or the specific path '/web_comunications/cms/'.
    Affected if MegaCMS is not present on the server.
  2. Identify MegaCMS version
    Locate the version file or header within the MegaCMS installation. Check version.php, about.php, or the main index file for a version identifier. Compare against v12.0.0.
    Affected if The installed version is MegaCMS v12.0.0.
  3. Verify vulnerable endpoint exists
    Check if the endpoint /web_comunications/cms/get_provincias exists on the server by reviewing the web directory structure and routing configuration.
    Affected if The endpoint /web_comunications/cms/get_provincias is present and accessible.
  4. Inspect parameter handling in source code
    Review the source code of the get_provincias functionality, specifically how the 'id_territorio' POST parameter is processed. Search for direct string concatenation in SQL queries.
    Affected if The 'id_territorio' parameter is used directly in SQL queries without parameterized queries or input validation.
  5. Test parameter for injection susceptibility
    Send a crafted POST request to /web_comunications/cms/get_provincias with the 'id_territorio' parameter containing SQL injection payloads (e.g., ' OR '1'='1). Observe if the application returns unexpected database errors or behaves differently.
    Affected if The application reflects SQL syntax errors or returns unexpected data based on injection payloads.

A user is affected if MegaCMS v12.0.0 is installed, the /web_comunications/cms/get_provincias endpoint exists, and the 'id_territorio' parameter accepts unsanitized SQL input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) for all database operations involving user input, and add robust input validation with allowlist filtering for the id_territorio parameter. Consider deploying a WAF as an interim protective control.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3325 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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