CVE-2026-2292
Stored XSS in Morkva UA Shipping WordPress Plugin Admin Settings
Publication date: 2026-03-04
Last updated on: 2026-03-04
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| morkva | ua_shipping_plugin | to 1.7.9 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | 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. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that you are not using versions of the Morkva UA Shipping plugin for WordPress up to and including 1.7.9.
Additionally, verify that your WordPress installation is not a multi-site setup or that the unfiltered_html setting is not disabled, as these conditions are required for the vulnerability to be exploitable.
Since the vulnerability requires administrator-level permissions, restrict access to trusted administrators only and monitor for any suspicious activity.
Can you explain this vulnerability to me?
The Morkva UA Shipping plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in all versions up to and including 1.7.9. This vulnerability arises because the plugin does not properly sanitize input or escape output in the admin settings. As a result, an attacker with administrator-level permissions can inject malicious web scripts into pages. These scripts will execute whenever a user accesses the affected page.
This vulnerability specifically affects multi-site WordPress installations or installations where the unfiltered_html setting is disabled.
How can this vulnerability impact me? :
This vulnerability allows an authenticated attacker with administrator-level permissions to inject malicious scripts into the website. These scripts can execute in the context of users visiting the injected pages, potentially leading to unauthorized actions such as stealing user credentials, performing actions on behalf of users, or spreading malware.
Because the vulnerability requires high privileges and affects multi-site or restricted HTML installations, the impact is somewhat limited but still significant in environments where these conditions are met.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know