Wd Instagram FeedWordPress extension · Web Dorado

CVE-2018-10301

MEDIUM · 6.1 CVSS v3.0 Published 2018-04-23

Fix available

A fix is available. Upgrade to 1.3.1 or later.

See remediation →

68/100

Remediation priority · Elevated

Remotely reachable No privileges

Official description

NVD · unedited

Cross-site scripting (XSS) vulnerability in the Web-Dorado Instagram Feed WD plugin before 1.3.1 Premium for WordPress allows remote attackers to inject arbitrary web script or HTML by passing payloads in a comment on an Instagram post.

Technical summary

dbcve analysis · high confidence

Cross-site scripting (XSS) vulnerability in the Web-Dorado Instagram Feed WD plugin for WordPress allows remote attackers to inject arbitrary web script or HTML via malicious payloads embedded in Instagram post comments. The injected script executes in the context of the victim's browser when viewing the affected Instagram feed.

MitigationUpdate the Web-Dorado Instagram Feed WD plugin to version 1.3.1 or later, which includes proper input sanitization and output encoding to prevent XSS attacks via Instagram comment fields.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Wd Instagram FeedWordPress extension

Affected:< 1.3.1

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm WordPress installation exists

Check for the presence of wp-content/plugins/ directory or access the WordPress admin dashboard at /wp-admin/

Affected if WordPress is not installed - the plugin cannot be present
Locate the Instagram Feed WD plugin files

Navigate to wp-content/plugins/ and look for a directory named 'wd-instagram-feed', 'instagram-feed-wd', or similar containing 'instagram' and 'wd' in the name

Affected if The plugin directory is not found - not affected
Determine the installed plugin version

Check the plugin's main PHP file for a 'Version:' header in the plugin comment block, or look in wp-content/plugins/[plugin-folder]/readme.txt for the 'Stable tag:' entry, or access WordPress admin > Plugins > Plugin Name to view the version displayed

Affected if The plugin version is 1.3.1 or higher - not vulnerable; if version cannot be determined or shows < 1.3.1, further investigation is needed
Verify the plugin is active

In WordPress admin, go to Plugins > Installed Plugins and check if the Instagram Feed WD plugin is activated, or query the wp_options table for option_name = 'active_plugins' and check for the plugin entry

Affected if The plugin is not installed or not active - not vulnerable since the vulnerable code is not executing
Confirm the plugin handles Instagram comments

Check if the plugin is configured to display Instagram feed content that includes comments, by visiting the plugin settings page or inspecting any frontend output from the plugin's shortcode

Affected if The plugin displays Instagram posts with embedded comments from Instagram - vulnerable to XSS via malicious comment content

A user is affected if the Web-Dorado Instagram Feed WD plugin is installed, active, and running at a version lower than 1.3.1 while configured to display Instagram feeds containing comments.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to 1.3.1 or later

Fixed in 1.3.1

Interim mitigation

Update the Web-Dorado Instagram Feed WD plugin to version 1.3.1 or later, which includes proper input sanitization and output encoding to prevent XSS attacks via Instagram comment fields.

Fix this in Wd Instagram Feed Scoped from the published advisory

Consultation2.0 h
Implementation3.0 h
Testing2.0 h
Review / QA1.0 h

8.0 hours of engineering $1,420

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-10301 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2018-10301?

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.

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

At a glance

A fix existsUpgrade to 1.3.1 or later

Severity 6.1 Medium

Exploit likelihood EPSS, next 30 days 1.0%

Affects: Wd Instagram Feed

Remediation

Need this fixed?

Fix this in Wd Instagram Feed 8 hrs · Moderate

Typical engagement from $1,420

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2018-10301 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References