CVE-2026-5293
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 · uneditedThe 診断ジェネレータ作成プラグイン (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.
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 · high confidenceThe Diagnosis Generator WordPress plugin versions up to 1.4.16 have a stored XSS vulnerability in the themeFunc() function hooked to admin_init. The function processes theme update requests without verifying user capabilities, allowing any authenticated user (including subscribers) to inject malicious JavaScript via the 'js' parameter into theme files. The save() function uses stripslashes() which removes WordPress's magic quotes protection, enabling the injection. The malicious script executes when users access pages with the diagnosis form shortcode.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Diagnosis Generator plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Diagnosis Generator', or check the plugins directory for the diagnosis-generator folderAffected if The plugin is installed and its version is 1.4.16 or lower
-
Verify the plugin versionCheck the plugin header in diagnosis-generator.php for the Version field, or look at the plugin details page in WordPress adminAffected if Version is 1.4.16 or any version up to and including 1.4.16
-
Confirm admin_init hook exists with themeFuncExamine the main plugin PHP file for add_action('admin_init', 'themeFunc') or similar registrationAffected if The themeFunc function is hooked to admin_init without a capability check like current_user_can()
-
Check for subscriber-level user accountsIn WordPress admin, go to Users and review roles; subscribers have the lowest privilege level but are still authenticated usersAffected if Any subscriber-level or higher user accounts exist in the WordPress installation
-
Inspect theme files for suspicious js parameter injectionLook in the active theme's PHP files (typically in wp-content/themes/THEMENAME/) for any injected script tags or JavaScript code that was added via the plugin's themeFunc processing of a 'js' parameterAffected if Unexpected script tags or JavaScript appear in theme files without manual editing by an administrator
-
Check if diagnosis form shortcode is in useSearch WordPress pages and posts for the shortcode [diagnosis_form] or similar diagnosis-related shortcodeAffected if The diagnosis form shortcode is present on any published page, as this is where the injected XSS would execute
A user is affected if the Diagnosis Generator plugin version 1.4.16 or lower is installed, the themeFunc is hooked to admin_init without capability checks, and either subscriber users exist or the diagnosis form shortcode is in use on the site.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to version 1.4.17 or later which adds proper authorization checks and input sanitization. Until patched, disable the plugin or ensure user registration is disabled to prevent subscriber-level access.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5293 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5293 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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