dbcve.org
Jayj QuicktagWordPress extension · Jayj Quicktag Project

CVE-2017-18546

HIGH · 8.8 CVSS v3.0 Published 2019-08-16
Fix available
A fix is available. Upgrade to 1.3.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 jayj-quicktag plugin before 1.3.2 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 · high confidence

The jayj-quicktag WordPress plugin before version 1.3.2 contains a Cross-Site Request Forgery (CSRF) vulnerability. Attackers could potentially trick authenticated administrators into unknowingly executing unwanted actions via maliciously crafted links or forms.

MitigationUpdate the jayj-quicktag plugin to version 1.3.2 or later to patch the CSRF vulnerability.

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
Jayj QuicktagWordPress extension
Affected:< 1.3.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.0/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. Check if Jayj Quicktag plugin is installed
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Jayj Quicktag' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'jayj-quicktag' or similar.
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed version of Jayj Quicktag
    In WordPress admin > Plugins > Installed Plugins, find Jayj Quicktag and read the version number displayed beneath the plugin name. Alternatively, check the plugin's main PHP file for a 'Version' header in the plugin comment block.
    Affected if The version displayed is lower than 1.3.2 or no version number is visible (which may indicate an old, unversioned release)
  3. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify whether Jayj Quicktag shows as 'Active' under the plugin status column.
    Affected if The plugin is active and running on the site

You are affected if the Jayj Quicktag plugin is installed and active on your WordPress site with a version number lower than 1.3.2, making authenticated administrators vulnerable to CSRF attacks.

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 1.3.2 or later
Fixed in 1.3.2
Interim mitigation

Update the jayj-quicktag plugin to version 1.3.2 or later to patch the CSRF vulnerability.

Fix this in Jayj Quicktag Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $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 $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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