dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-48346

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Missing Authorization vulnerability in Embed360 Embed and Integrate Etsy Shop embed-and-integrate-etsy-shop allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Embed and Integrate Etsy Shop: from n/a through <= 1.0.8.

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 confidence

Missing authorization vulnerability in Embed360's Etsy Shop integration plugin allows unauthenticated or unauthorized users to access functionality that should be restricted by access control lists (ACLs). The vulnerability exists in versions up to and including 1.0.8, potentially enabling unauthorized actions or data access.

MitigationUpdate to the latest version of the plugin once available. If no patch exists, conduct a thorough code review to identify and implement proper authorization checks on all sensitive functions and restrict access at the server level as a temporary measure.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Embed360 Etsy Shop plugin is installed
    Navigate to your plugin management interface (typically wp-admin > Plugins) and look for 'Embed360 Etsy Shop integration' or similar naming. If using CLI, search the wp-content/plugins directory for embed360 or etsy-related plugin folders.
    Affected if The plugin named 'Embed360 Etsy Shop integration' or variants like 'Embed360 Etsy' is found installed on the system.
  2. Identify the installed plugin version
    In the plugin management UI, click on the plugin to view its details and locate the version number. Alternatively, inspect the main plugin file header (usually plugin-name.php in the plugin folder) for the 'Version' tag.
    Affected if The installed version is 1.0.8 or any version lower than 1.0.8 (e.g., 1.0.7, 1.0.6, 1.0.5, etc.).
  3. Verify if public-facing Etsy shop endpoints exist without authentication
    Access the site's public URLs that typically handle Etsy shop functionality (such as /etsy-shop, /embed360/etsy, or similar routes exposed by the plugin). Attempt to access these endpoints without logging in or providing any credentials.
    Affected if The endpoints return valid shop data or functional responses without requiring login or showing any authorization prompt.
  4. Check for exposed API routes or AJAX actions
    Review the plugin's publicly accessible AJAX action hooks (usually wp_ajax_ and wp_ajax_nopriv_ prefixed actions). Inspect the plugin code for any action handlers registered without proper capability checks or user validation.
    Affected if AJAX actions are registered with 'nopriv' capability (accessible to unauthenticated users) and lack proper authorization logic inside the handler functions.
  5. Inspect ACL or capability settings within plugin configuration
    Locate the plugin's settings panel (typically under Settings or a dedicated menu item in wp-admin). Look for access control, permission, or ACL configuration options and verify if they enforce user role restrictions.
    Affected if No role-based access control settings exist, or the plugin configuration allows 'guest' or 'public' access to sensitive shop management functions.

You are affected if the Embed360 Etsy Shop integration plugin is installed at version 1.0.8 or lower AND the plugin exposes functional endpoints or API actions that can be accessed without authentication or proper authorization validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the plugin once available. If no patch exists, conduct a thorough code review to identify and implement proper authorization checks on all sensitive functions and restrict access at the server level as a temporary measure.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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