dbcve.org
Tag MinerWordPress extension · Fossura

CVE-2016-10978

HIGH · 8.8 CVSS v3.1 Published 2019-09-17
Fix available
A fix is available. Upgrade to after 1.1.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
The fossura-tag-miner plugin before 1.1.5 for WordPress has CSRF.

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

The fossura-tag-miner WordPress plugin before version 1.1.5 contains a Cross-Site Request Forgery (CSRF) vulnerability. Attackers can craft malicious requests that trick authenticated administrators into performing unintended actions within the plugin, such as modifying settings or triggering plugin functions without their explicit consent.

MitigationUpdate the fossura-tag-miner plugin to version 1.1.5 or later to obtain the patched version that includes proper CSRF protection mechanisms.

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
Tag MinerWordPress extension
Affected:<= 1.1.2

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Locate the fossura-tag-miner plugin files
    Check the WordPress plugins directory at /wp-content/plugins/ for a folder named fossura-tag-miner. If the folder exists, the plugin is installed.
    Affected if The plugin folder exists in the WordPress installation.
  2. Read the plugin header for version number
    Open the main plugin file (usually fossura-tag-miner.php) in the plugin folder and locate the Version header in the plugin comment block at the top of the file.
    Affected if The version shown is 1.1.2 or lower.
  3. Verify version via WordPress admin interface
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and locate 'Fossura Tag Miner' in the list. The version number is displayed beneath the plugin name.
    Affected if The displayed version is 1.1.2 or lower.
  4. Confirm plugin is active
    In the WordPress admin under Plugins > Installed Plugins, verify that the Fossura Tag Miner plugin is activated (the 'Activate' link is not present, or the plugin shows as active).
    Affected if The plugin is active and the version is 1.1.2 or lower.

The environment is affected if the fossura-tag-miner plugin is installed, active, and running version 1.1.2 or lower.

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 a release after 1.1.2
Interim mitigation

Update the fossura-tag-miner plugin to version 1.1.5 or later to obtain the patched version that includes proper CSRF protection mechanisms.

Fix this in Tag Miner Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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