CVE-2026-5293
Deferred Deferred - Pending Action
Stored XSS in Diagnosis Generator WordPress Plugin

Publication date: 2026-05-20

Last updated on: 2026-05-20

Assigner: Wordfence

Description
The 診断ジェネレータ作成プラグイン (Diagnosis Generator) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'js' parameter in versions up to and including 1.4.16. This is due to missing authorization checks and insufficient input sanitization in the themeFunc() function. The function is hooked to 'admin_init' and processes theme update requests without verifying user capabilities, allowing any authenticated user (including subscribers) to save malicious JavaScript to theme files. Additionally, the save() function uses stripslashes() which removes WordPress's magic quotes protection. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in theme files that will execute whenever a user accesses a page containing the diagnosis form shortcode.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-20
Last Modified
2026-05-20
Generated
2026-05-20
AI Q&A
2026-05-20
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
diagnosis_generator plugin to 1.4.16 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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
Can you explain this vulnerability to me?

The 診断ジェネレータ作成プラグイン (Diagnosis Generator) plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in versions up to and including 1.4.16. This vulnerability arises because the plugin's themeFunc() function, which handles theme update requests, lacks proper authorization checks and input sanitization. As a result, any authenticated user, even those with subscriber-level access, can inject malicious JavaScript code into theme files via the 'js' parameter. The save() function further weakens security by using stripslashes(), which removes WordPress's magic quotes protection, making it easier to save harmful scripts. These scripts execute whenever a user visits a page containing the diagnosis form shortcode.


How can this vulnerability impact me? :

This vulnerability allows attackers with subscriber-level access or higher to inject arbitrary JavaScript into theme files. The injected scripts execute in the context of users visiting pages with the diagnosis form shortcode, potentially leading to theft of user credentials, session hijacking, defacement, or distribution of malware. Because the vulnerability requires only authenticated access, it increases the risk from lower-privileged users and can compromise the security and integrity of the affected WordPress site.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

Detection of this vulnerability involves checking for the presence of malicious JavaScript injected into theme files via the 'js' parameter in the 診断ジェネレータ作成プラグイン (Diagnosis Generator) plugin for WordPress. Since the vulnerability allows authenticated users to save malicious scripts in theme files, inspecting these files for unexpected JavaScript code is essential.

You can use commands to search for suspicious JavaScript code or unusual modifications in theme files. For example, on a Linux server hosting WordPress, you might run:

  • grep -r --include='*.php' '<script' wp-content/themes/
  • grep -r 'js=' wp-content/plugins/diagnosis_generator/

Additionally, monitoring web server logs for unusual POST requests to admin endpoints related to theme updates or the diagnosis form shortcode usage may help detect exploitation attempts.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include updating the 診断ジェネレータ作成プラグイン (Diagnosis Generator) plugin to a version later than 1.4.16 where the vulnerability is fixed.

If an update is not yet available, restrict access to the WordPress admin area to trusted users only, especially limiting subscriber-level users from accessing theme update functionalities.

Additionally, review and sanitize theme files to remove any injected malicious JavaScript code.

Implement monitoring for unauthorized changes to theme files and consider disabling or removing the vulnerable plugin until a patch is applied.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows authenticated users with subscriber-level access to inject arbitrary JavaScript into theme files, which can execute when other users access pages containing the diagnosis form shortcode.

Such stored cross-site scripting (XSS) vulnerabilities can lead to unauthorized access to user data, session hijacking, or other malicious activities that compromise data confidentiality and integrity.

This can negatively impact compliance with data protection regulations like GDPR and HIPAA, which require appropriate safeguards to protect personal and sensitive information from unauthorized access or disclosure.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart