CVE-2014-6047
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 · uneditedphpMyFAQ before 2.8.13 allows remote authenticated users with certain permissions to read arbitrary attachments by leveraging incorrect "download an attachment" permission checks.
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 confidencephpMyFAQ before version 2.8.13 contains a flawed permission check in the attachment download functionality. Authenticated users with limited permissions can bypass intended access controls to read arbitrary file attachments stored in the system, leading to unauthorized information disclosure.
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< 2.8.13CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify phpMyFAQ installation versionLocate the version file (typically version.php in the main directory or check the admin dashboard's system info page) and note the reported version numberAffected if The installed version is below 2.8.13 (e.g., 2.8.0 through 2.8.12)
-
Confirm attachment storage is in useCheck if the $faqconfig['attachment.enableAttachments'] setting is enabled in the config file (usually config/constants.php or a similar configuration file), or look for an 'attachments' directory in the phpMyFAQ installationAffected if Attachment functionality is enabled and the system stores uploaded files
-
Verify user authentication is activeConfirm that phpMyFAQ user authentication is enabled and users can log in with standard user accountsAffected if The system allows authenticated user sessions, particularly for non-admin users with limited permissions
-
Check attachment download endpoint accessibilityAttempt to access the attachment download script (typically attachment.php or a similar endpoint in the main phpMyFAQ directory) while logged in as a low-privilege user accountAffected if The download functionality is accessible without proper permission validation on attachment files
The environment is affected if phpMyFAQ version is below 2.8.13 AND the attachment download feature is enabled and accessible to authenticated users with limited permissions.
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 data2.8.13
Upgrade phpMyFAQ to version 2.8.13 or later which contains the corrected permission validation for attachment downloads. If immediate patching is not possible, review and restrict user attachment permissions as a compensating control.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6047 — 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-2014-6047 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