dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-15363

MEDIUM · 5.9 CVSS v3.1 Published 2026-03-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/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
The Get Use APIs WordPress plugin before 2.0.10 executes imported JSON, which could allow users with a role as low as contributor to perform Cross-Site Scripting attacks under certain server configurations.

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

The Get Use APIs WordPress plugin before version 2.0.10 fails to properly sanitize imported JSON data before executing/rendering it, creating a stored Cross-Site Scripting (XSS) vulnerability. Users with contributor-level permissions can import malicious JSON containing script payloads that execute when viewed by other users.

MitigationUpdate the Get Use APIs plugin to version 2.0.10 or later to patch the unsafe JSON execution. If the updated version is unavailable, disable the plugin or implement input validation/WAF rules to block script-containing JSON payloads.

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

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

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 Get Use APIs plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Get Use APIs' in the list, or inspect the plugins directory for a folder named 'get-use-apis' or similar
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In the Plugins list, find the Get Use APIs plugin and compare the version number shown against version 2.0.10. Alternatively, check the plugin's main PHP file header for the Version field
    Affected if The installed version is lower than 2.0.10 (e.g., 2.0.9, 2.0.8, etc.)
  3. Verify the JSON import feature exists
    Locate the plugin settings or admin menu for Get Use APIs and look for an import function that accepts JSON data. Check the plugin code for import-related functions handling JSON input
    Affected if The plugin includes functionality to import or upload JSON data from users
  4. Confirm contributor-level or higher users exist
    Check WordPress user roles under Users > All Users to see if any accounts have Contributor, Author, Editor, or Administrator roles, as these roles can access the plugin import feature
    Affected if There are users with contributor-level permissions or higher who can access the import functionality

A user is affected if the Get Use APIs plugin is installed with a version lower than 2.0.10, the plugin has a JSON import feature, and users with contributor-level or higher permissions can access that import functionality.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Get Use APIs plugin to version 2.0.10 or later to patch the unsafe JSON execution. If the updated version is unavailable, disable the plugin or implement input validation/WAF rules to block script-containing JSON payloads.

Recommended fix Moderate confidence

Get Use APIs WordPress plugin version 2.0.10 or later

  1. Locate the Get Use APIs plugin in your WordPress installation
  2. Navigate to Plugins > Installed Plugins
  3. Find Get Use APIs in the plugin list
  4. Check the current version number
  5. If the version is below 2.0.10, click Update Now or manually download version 2.0.10 or later from the WordPress plugin repository
  6. Verify the update completed successfully
  7. Confirm the running version is 2.0.10 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed 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 help mitigating

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-2025-15363 — 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-15363 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