CVE-2026-7209
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 Simple Link Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `qcopd-directory` shortcode in all versions up to, and including, 8.9.2. This is due to insufficient input sanitization and output escaping on user supplied attributes such as `title_font_size`. This makes it possible for authenticated attackers, with contributor-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 Simple Link Directory WordPress plugin (versions up to 8.9.2) contains a stored XSS vulnerability in its qcopd-directory shortcode. The title_font_size parameter accepts user input without proper sanitization or output escaping, allowing authenticated contributors+ to inject malicious JavaScript that executes in victims' browsers when viewing infected pages.
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.
-
Verify Simple Link Directory plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Simple Link Directory' or 'qcopd' in the plugin list. Note the installed version number displayed next to the plugin name.Affected if Plugin is installed and version is 8.9.2 or lower
-
Confirm plugin version is within affected rangeCompare the installed version you found to 8.9.2. The vulnerability exists in versions up to and including 8.9.2.Affected if Installed version is 8.9.2 or any lower version number
-
Identify pages using the qcopd-directory shortcodeSearch your WordPress database for posts/pages containing the shortcode [qcopd-directory]. You can use phpMyAdmin to query the wp_posts table: SELECT * FROM wp_posts WHERE post_content LIKE '%[qcopd-directory%' AND post_status='publish';Affected if Any published content contains the [qcopd-directory] shortcode
-
Check if title_font_size parameter is in useExamine the shortcode instances found. Look for usage of the title_font_size attribute, for example: [qcopd-directory title_font_size="..."]. Check the attribute values for any unsanitized user-supplied values.Affected if The shortcode is used with a title_font_size parameter containing unsanitized input
You are affected if the Simple Link Directory plugin is installed at version 8.9.2 or lower AND any published page/post contains the qcopd-directory shortcode with a title_font_size parameter.
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 the plugin to a version beyond 8.9.2 if available, or implement proper input sanitization (sanitize_text_field, esc_attr) and output escaping (esc_html, esc_attr) on all shortcode attributes before rendering.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7209 — 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-7209 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