CVE-2025-43949
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 · uneditedMuM (aka Mensch und Maschine) MapEdit (aka mapedit-web) 24.2.3 is vulnerable to SQL Injection that allows an attacker to execute malicious SQL statements that control a web application's database server.
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 confidenceMuM MapEdit (mapedit-web) version 24.2.3 contains a SQL Injection vulnerability that allows unauthenticated attackers to inject malicious SQL statements via unsanitized user input, potentially enabling full database compromise, data exfiltration, or remote code execution through database functions.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 installed MuM MapEdit versionLocate the installed version of mapedit-web in your environment. Check application metadata, version files, or the web interface about/login page for the version display.Affected if The installed version is 24.2.3 or falls within the affected version range containing 24.2.3
-
Determine web interface exposureAssess whether the mapedit-web application is accessible to unauthenticated users or untrusted network segments. Review network configuration and authentication enforcement.Affected if The web interface permits unauthenticated access from any network location
-
Inspect database query handling codeExamine the application source code for database interaction patterns. Locate SQL query execution points and verify whether user-supplied input is directly concatenated into query strings or properly parameterized.Affected if User input is directly concatenated into SQL queries without sanitization or prepared statement usage
-
Review input validation implementationCheck if input validation and sanitization mechanisms are applied to user-facing parameters before they reach database query functions.Affected if No input validation exists or validation can be bypassed for SQL-relevant parameters
You are affected if MuM MapEdit version 24.2.3 is installed AND the web interface is exposed to unauthenticated users AND database queries use unsanitized user input.
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 dataUpgrade to vendor-patched version if available; otherwise, implement parameterized queries/prepared statements for all database interactions and apply input validation to eliminate SQL injection vectors.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43949 — 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-43949 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