dbcve.org
LetodmsApplication · Letodms Project

CVE-2012-4570

CRITICAL · 9.8 CVSS v3.0 Published 2017-10-23
Fix available
A fix is available. Upgrade to after 3.3.7 or later.
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 vulnerability in LetoDMS_Core/Core/inc.ClassDMS.php in LetoDMS (formerly MyDMS) before 3.3.8 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 confidence

SQL injection vulnerability in LetoDMS (formerly MyDMS) Core inc.ClassDMS.php affecting versions prior to 3.3.8. The vulnerability allows remote attackers to execute arbitrary SQL commands through unspecified input vectors, potentially enabling complete database compromise, data exfiltration, or further system access.

MitigationUpgrade to LetoDMS version 3.3.8 or later which contains the security patch for this SQL injection vulnerability. If immediate upgrade is not possible, restrict network access to the application and implement WAF rules as a temporary compensating control.

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
LetodmsApplication
Affected:<= 3.3.7

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.0/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 checks

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

  1. Identify LetoDMS version
    Check the version file or header typically included in the LetoDMS installation. Common locations include a version.php file, the installer info, or the application footer/admin panel which often displays the software version.
    Affected if The installed version is 3.3.7 or any version prior to 3.3.8 (e.g., 3.3.6, 3.3.5, etc.)
  2. Verify vulnerable file exists
    Locate the file inc.ClassDMS.php in the LetoDMS installation directory. This file is the component containing the SQL injection vulnerability.
    Affected if The file inc.ClassDMS.php exists in the installation and the version is <= 3.3.7
  3. Confirm application is accessible
    Verify the LetoDMS web application is accessible and processing requests. SQL injection requires the vulnerable code to execute within the application context.
    Affected if The LetoDMS application is accessible and running with a version <= 3.3.7

A user is affected if LetoDMS version 3.3.7 or earlier is installed and the application is accessible, as this version contains the SQL injection vulnerability in inc.ClassDMS.php.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.3.7
Interim mitigation

Upgrade to LetoDMS version 3.3.8 or later which contains the security patch for this SQL injection vulnerability. If immediate upgrade is not possible, restrict network access to the application and implement WAF rules as a temporary compensating control.

Recommended fix High confidence

LetoDMS 3.3.8 or later

  1. 1. Create a complete backup of the LetoDMS database and application files before proceeding.
  2. 2. Download LetoDMS version 3.3.8 or later from the official SourceForge repository.
  3. 3. If running a standard installation, replace the application files with the new version, preserving any custom configurations.
  4. 4. Specifically ensure the LetoDMS_Core/Core/inc.ClassDMS.php file is updated to the fixed version.
  5. 5. Verify database schema compatibility and run any provided upgrade scripts.
  6. 6. Test the application functionality to ensure normal operations work correctly.
  7. 7. Verify the fix by checking that the SQL injection vulnerability is no longer present in the updated inc.ClassDMS.php file.
Caveat Review release notes for any configuration or database schema changes that may require adjustments during upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Letodms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-4570 — 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-2012-4570 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