CVE-2010-3922
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 in Movable Type 4.x before 4.35 and 5.x before 5.04 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
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 · moderate confidenceSQL injection vulnerability in Movable Type CMS affecting versions 4.x before 4.35 and 5.x before 5.04 allows remote unauthenticated attackers to execute arbitrary SQL commands via unspecified vectors, enabling potential data exfiltration or complete database compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 4.0= 4.1= 4.2= 4.3= 4.23= 4.25= 4.26= 4.31= 4.32= 4.33= 4.34= 4.261CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 Movable Type installationCheck for Movable Type by looking for mt-config.cgi or mt.cgi in the web root directory. Common paths include /cgi-bin/mt/ or the main web directory.Affected if Movable Type CMS is present on the server
-
Determine installed Movable Type versionOpen mt/mt-config.cgi and look for the 'version' setting, or check the mt-static/css/main.css file for a version comment. Alternatively, access the mt.cgi login page which often displays version information.Affected if The version displayed is 4.x (4.0 to 4.34) or 5.x (5.0 to 5.03)
-
Confirm version is in vulnerable rangeCompare your installed version number against the affected ranges: 4.0 through 4.34, or 5.0 through 5.03. Versions 4.35+ and 5.04+ are patched.Affected if Installed version is less than 4.35 (for 4.x line) or less than 5.04 (for 5.x line)
-
Verify web interface is accessibleCheck if mt.cgi or mt-minimal.cgi is accessible from the network. Test with a curl or browser request to theMovable Type CGI scripts.Affected if The Movable Type web interface is exposed to network users without authentication restrictions
-
Check database configuration exposureReview mt-config.cfg or mt-config.cgi for database connection details. The vulnerability allows SQL injection that could access or modify this data.Affected if Database credentials in the Movable Type configuration are accessible to the compromised application
You are affected if Movable Type CMS versions 4.0 through 4.34 or 5.0 through 5.03 are installed and accessible via the web.
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 Movable Type to version 4.35 or 5.04 or later to patch the SQL injection vulnerability. If immediate upgrade is not feasible, implement WAF rules to filter malicious SQL payloads and restrict database privileges to application service accounts.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3922 — 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-2010-3922 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