CVE-2012-1078
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 · uneditedThe System Utilities (sysutils) extension 1.0.3 and earlier for TYPO3 allows remote attackers to obtain sensitive information via unspecified vectors related to improper "protection" of the "backup output directory."
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 confidenceThe sysutils extension for TYPO3 versions 1.0.3 and earlier has an information disclosure vulnerability where the backup output directory is not properly protected. This allows remote attackers to potentially access sensitive backup files containing system configuration, database credentials, or other confidential data through unspecified vectors.
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<= 1.0.3= 0.10.0= 1.0.0= 1.0.1= 1.0.2CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Verify sysutils extension is installedIn TYPO3 backend, navigate to Extension Manager > Extensions and search for 'sysutils', or check the file typo3conf/ext/sysutils/ext_emconf.php for the version numberAffected if The extension is present and its version is 1.0.3 or lower, or matches 0.10.0, 1.0.0, 1.0.1, or 1.0.2
-
Identify the backup output directory locationCheck the extension configuration in TYPO3 backend or inspect typo3conf/ext/sysutils/ext_localconf.php for the backup path settingAffected if The extension has a backup output directory configured and the path is within or accessible from the web root (typo3/ or fileadmin/ directories)
-
Confirm the backup directory is web-accessibleAttempt to directly access the backup output directory via HTTP request (e.g., curl or browser request to the directory URL)Affected if The directory responds to HTTP requests and lists or serves files without authentication
-
Check for existing backup filesList files in the configured backup output directory using command line (ls, dir) or file managerAffected if Any .sql, .tar, .gz, .zip, or similar backup files exist in the web-accessible directory
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 dataEnsure the backup output directory is not web-accessible by moving it outside the web root, adding .htaccess password protection, or disabling the backup functionality until an updated extension version is available. Verify that no backup files are publicly accessible.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1078 — 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-2012-1078 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