VulnerabilityPublished 18 Mar 2026

CVE-2025-15363: Get Use APIs (WordPress plugin) · Cross-Site Scripting (XSS)

Affects Get Use APIs (WordPress plugin)Source CVE Database V5

Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 2.0.10 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.0.10

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Get Use APIs (WordPress plugin) to 2.0.10.

Affected software

Product	Affected	Fixed in
Get Use APIs	Affected <2.0.10	Fixed in 2.0.10

AI-suggested

To mitigate CVE-2025-15363 effectively, organizations should take the following specific actions: 1) Immediately audit WordPress sites for the presence of the Get Use APIs plugin and identify versions prior to 2.0.10. 2) Apply updates to version 2.0.10 or later as soon as the patch becomes available, or contact the plugin vendor for interim fixes or workarounds. 3) Restrict contributor role permissions by limiting the number of users assigned this role and reviewing their activities regularly. 4) Implement strict input validation and output encoding on any JSON import functionality, ensuring that imported data cannot execute scripts. 5) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious JSON payloads or script injections targeting the plugin's endpoints. 6) Monitor logs for unusual contributor activity or unexpected JSON imports. 7) Educate content contributors about security best practices and the risks of importing untrusted data. 8) Consider temporarily disabling the JSON import feature if it is not essential, reducing the attack surface. 9) Regularly back up website data and configurations to enable quick recovery in case of compromise. These targeted measures go beyond generic advice by focusing on the specific attack vector and user roles involved in this vulnerability.

Description

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.

Impact

The impact of CVE-2025-15363 on organizations worldwide can be substantial, especially for those relying on the Get Use APIs plugin in their WordPress installations. Since contributor-level users can exploit this vulnerability, attackers can inject malicious scripts that execute in the browsers of site visitors or administrators. This can lead to session hijacking, allowing attackers to impersonate legitimate users and potentially escalate privileges or perform unauthorized actions. The injected scripts could also be used to deface websites, damaging brand reputation and user trust. Additionally, attackers might redirect users to phishing or malware distribution sites, increasing the risk of broader compromise. For organizations handling sensitive data or operating e-commerce platforms, such attacks could result in data breaches, financial loss, and regulatory penalties. The vulnerability also increases the attack surface by enabling insider threats or compromised contributor accounts to be leveraged for malicious purposes. Although no known exploits are currently in the wild, the ease of exploitation and low privilege requirement mean that the risk of future attacks is high. The impact extends beyond individual sites to potentially affect the broader WordPress ecosystem, given the plugin's usage in multiple countries and sectors.

CWE-79Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/428d08bb-5329-4406-a785-131bae4ed085/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Mar 2026, 06:43 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats