dbcve.org
Insert Or Embed Articulate ContentWordPress extension · Elearningfreak

CVE-2019-15649

HIGH · 8.8 CVSS v3.0 Published 2019-08-27
Fix available
A fix is available. Upgrade to 4.2999 or later.
See remediation →
94/100
Remediation priority · Urgent
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
The insert-or-embed-articulate-content-into-wordpress plugin before 4.2999 for WordPress has insufficient restrictions on file upload.

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 insert-or-embed-articulate-content-into-wordpress plugin before version 4.2999 contains insufficient restrictions on file upload functionality, allowing attackers to potentially upload arbitrary files including malicious executables.

MitigationUpgrade the plugin to version 4.2999 or later which contains proper file upload restrictions; if the plugin is not needed, remove it entirely.

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
Insert Or Embed Articulate ContentWordPress extension
Affected:< 4.2999

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

CVSS:3.0/AV:N/AC:L/PR:L/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. Verify plugin is installed
    Navigate to WordPress Admin > Plugins and search for 'Elearningfreak Insert Or Embed Articulate Content' or 'insert-or-embed-articulate-content-into-wordpress' in the installed plugins list
    Affected if Plugin appears in the plugins directory
  2. Check installed version
    In WordPress Admin > Plugins page, locate the plugin and read the version number displayed beneath the plugin name
    Affected if Version is less than 4.2999
  3. Confirm plugin is active
    In WordPress Admin > Plugins, verify the plugin status shows as 'Active' - only active plugins can process file uploads
    Affected if Plugin is active and version is below 4.2999

The environment is affected if the plugin is installed, active, and running a version lower than 4.2999 since the vulnerable file upload functionality would be accessible

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

Upgrade the plugin to version 4.2999 or later which contains proper file upload restrictions; if the plugin is not needed, remove it entirely.

Fix this in Insert Or Embed Articulate Content Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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