Wd Instagram FeedWordPress extension · Web Dorado
CVE-2018-10300
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 · uneditedCross-site scripting (XSS) vulnerability in the Web-Dorado Instagram Feed WD plugin before 1.3.1 for WordPress allows remote attackers to inject arbitrary web script or HTML by passing payloads in an Instagram profile's bio.
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 confidenceStored XSS vulnerability in the Web-Dorado Instagram Feed WD plugin allows attackers to inject malicious JavaScript/HTML through Instagram profile bio fields. The plugin fails to properly sanitize bio content before rendering it in the feed, causing the payload to execute in users' browsers.
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
Wd Instagram FeedWordPress extension
< 1.3.1CVSS 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
- 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? 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.
-
Verify Web Dorado Wd Instagram Feed plugin is installedLog into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the plugins directory for 'wd-instagram-feed' or 'web-dorado-instagram-feed' folderAffected if The plugin is present in the WordPress installation
-
Identify installed plugin versionIn WordPress admin, find the plugin in the Plugins list and check the version number displayed beneath the plugin name, or read the main plugin PHP file and look for the 'Version' header in the plugin comment blockAffected if Version is lower than 1.3.1 (e.g., 1.3.0, 1.2.x, 1.1.x, etc.)
-
Check if Instagram feeds are configured to display profile bioReview the plugin's widget or shortcode settings in WordPress admin. Look for options related to displaying Instagram profile information, bio, or biography fields in the feed display settingsAffected if Feeds are configured to render profile bio information from Instagram accounts
-
Inspect rendered output for unsanitized bio contentView a page or post containing an Instagram feed shortcode or widget in a browser. Right-click and Inspect Element on the profile section to see if bio text is being rendered without HTML entity encoding (e.g., actual script tags visible in plain text rather than as escaped entities)Affected if Raw HTML or JavaScript from the Instagram bio field appears unescaped in the page source
A user is affected if the Web Dorado Wd Instagram Feed plugin version is below 1.3.1 AND Instagram feeds displaying profile bio fields are active on the site.
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 data1.3.1
Upgrade to version 1.3.1 or later which implements proper sanitization of Instagram profile bio fields before output.
Fix this in Wd Instagram Feed
Scoped from the published advisory
- Consultation1.0 h
- Implementation3.0 h
- Testing2.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 $1,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10300 — 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-2018-10300 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