dbcve.org
Embed Any DocumentWordPress extension · Awsm

CVE-2023-23707

MEDIUM · 5.4 CVSS v3.1 Published 2023-03-23
Fix available
A fix is available. Upgrade to after 2.7.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), Unrestricted Upload of File with Dangerous Type vulnerability in Awsm Innovations Embed Any Document – Embed PDF, Word, PowerPoint and Excel Files allows Stored XSS via upload of SVG and HTML files. This issue affects Embed Any Document – Embed PDF, Word, PowerPoint and Excel Files plugin <= 2.7.1 versions.

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 Embed Any Document WordPress plugin versions 2.7.1 and below improperly handles file uploads, allowing attackers to upload SVG and HTML files containing malicious JavaScript. Since these files are served without proper sanitization, the embedded scripts execute in the context of other users' browsers, enabling stored XSS attacks.

MitigationUpgrade to the latest version of the plugin (2.7.2 or higher). Until patched, disable the document upload feature and restrict file type uploads to safe formats only.

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
Embed Any DocumentWordPress extension
Affected:<= 2.7.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Confirm the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Embed Any Document' or 'Awsm Embed Any Document'. If not visible in the list, check the /wp-content/plugins/ directory for a folder named 'embed-any-document' or similar.
    Affected if The plugin is not found in the WordPress installation.
  2. Identify the installed version
    In the WordPress plugins list, click on the plugin to view details, or open the main plugin file (usually embed-any-document.php) and look for the version comment/header at the top.
    Affected if The reported version is 2.7.1 or lower.
  3. Check if file uploads are enabled in plugin settings
    Go to the plugin settings page (usually under Settings or the plugin's own menu item) and look for upload options, file type restrictions, or document source settings.
    Affected if File upload or document embedding from external URLs is enabled and accessible to users.
  4. Inspect allowed file types in plugin configuration
    In the plugin settings, examine any option that controls allowed file extensions or document types (often labeled as 'Allowed file types', 'File extensions', or similar).
    Affected if SVG, HTML, or other potentially dangerous file types are listed as permitted.
  5. Review uploaded files on the site
    Check the /wp-content/uploads/ directory (or media library) for SVG or HTML files that may have been uploaded through the plugin.
    Affected if SVG or HTML files exist in the uploads folder that were added via the plugin's upload feature.

The environment is affected if the Awsm Embed Any Document plugin version 2.7.1 or lower is installed, active, and its upload feature allows SVG or HTML file uploads to users.

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 2.7.1
Interim mitigation

Upgrade to the latest version of the plugin (2.7.2 or higher). Until patched, disable the document upload feature and restrict file type uploads to safe formats only.

Fix this in Embed Any Document 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-2023-23707 — 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-2023-23707 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