dbcve.org
PhpmyfaqApplication

CVE-2014-6045

HIGH · 7.2 CVSS v3.0 Published 2018-08-28
Fix available
A fix is available. Upgrade to 2.8.13 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 phpMyFAQ before 2.8.13 allows remote authenticated users with certain permissions to execute arbitrary SQL commands via vectors involving the restore function.

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 confidence

SQL injection vulnerability in phpMyFAQ's restore function allows authenticated users with certain permissions to execute arbitrary SQL commands by injecting malicious SQL through unsanitized input parameters.

MitigationUpgrade phpMyFAQ to version 2.8.13 or later to obtain the vendor patch that properly sanitizes input in the restore function.

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
PhpmyfaqApplication
Affected:< 2.8.13

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:H/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 phpMyFAQ installation and version
    Locate the phpMyFAQ installation directory and check the version.php file or the admin dashboard footer for the installed version number
    Affected if The installed version is lower than 2.8.13
  2. Verify the restore function is enabled
    Access the phpMyFAQ admin panel and navigate to the backup/restore section to confirm the restore functionality is available and not disabled
    Affected if The restore function is enabled and accessible in the admin interface
  3. Check for users with restore permissions
    Review user accounts and roles in the phpMyFAQ admin panel to identify authenticated users granted restore or backup permissions
    Affected if Any authenticated user account exists with permissions to access the restore feature
  4. Confirm restore input handling
    Attempt a test restore operation or examine the restore.php file source code to observe whether SQL parameters are processed without sanitization
    Affected if The restore function accepts user-supplied input that is passed directly to SQL queries without proper escaping or parameterization

You are affected if phpMyFAQ version is below 2.8.13 AND the restore function is accessible to any authenticated user with restore permissions in your environment

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.

From vendor data
Upgrade available Upgrade to 2.8.13 or later
Fixed in 2.8.13
Interim mitigation

Upgrade phpMyFAQ to version 2.8.13 or later to obtain the vendor patch that properly sanitizes input in the restore function.

Fix this in Phpmyfaq Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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