CVE-2026-3350
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 Image Alt Text Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the post title in all versions up to, and including, 1.8.2. This is due to insufficient input sanitization and output escaping when dynamically generating image alt and title attributes using a DOM parser. This makes it possible for authenticated attackers, with Author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 Image Alt Text Manager plugin for WordPress fails to properly sanitize and escape user input when processing post titles that are used to dynamically generate image alt and title attributes via a DOM parser. This allows authenticated attackers with Author-level permissions or higher to inject malicious JavaScript code into stored post titles, which executes when other users view pages containing the affected images.
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.
-
Confirm Image Alt Text Manager plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Image Alt Text Manager' in the list. Note the installed version displayed.Affected if The plugin is present and the version is below 1.8.3
-
Verify the plugin version against the affected rangeCompare the installed version number to the vulnerable range. Versions prior to 1.8.3 are affected. The fixed version is 1.8.3.Affected if Installed version is lower than 1.8.3 (e.g., 1.8.2, 1.8.1, 1.8.0, etc.)
-
Check if post titles are used for alt/title attributesNavigate to the plugin settings (typically under Settings > Image Alt Text Manager or Media > Alt Text). Look for options that enable using post titles as image alt or title attributes.Affected if The feature that maps post titles to image alt/title attributes is enabled and the plugin version is below 1.8.3
-
Inspect stored post titles for injected scriptsIn WordPress admin, go to Posts > All Posts. Review post titles for unusual characters, HTML tags, or JavaScript code (such as <script>, javascript:, onerror=, onload=). Alternatively, query the wp_posts table directly for suspicious patterns in post_title.Affected if Post titles contain unsanitized JavaScript code and the plugin processes these titles for image attributes
The environment is affected if the Image Alt Text Manager plugin is installed with a version below 1.8.3 and the post title-to-attribute feature is enabled, or if malicious scripts are already present in stored post titles.
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 dataUpgrade to version 1.8.3 or later, which includes proper input sanitization and output escaping. If immediate upgrading is not possible, restrict the Author role capability pending the patch.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3350 — 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-3350 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