dbcve.org
Permalinks CustomizerWordPress extension · Yasglobal

CVE-2023-47773

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to after 2.8.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in YAS Global Team Permalinks Customizer plugin <= 2.8.2 versions.

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 · moderate confidence

This is a stored Cross-site Scripting (XSS) vulnerability in the YAS Global Team Permalinks Customizer WordPress plugin. The plugin fails to properly sanitize user-supplied input before rendering it in web pages, allowing authenticated attackers to inject malicious JavaScript code that executes in the browsers of users who view the affected pages.

MitigationUpdate the plugin to a version newer than 2.8.2. If no patched version is available, disable the plugin until a fix is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Permalinks CustomizerWordPress extension
Affected:<= 2.8.2

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check plugin version in WordPress admin
    Navigate to Plugins > Installed Plugins in the WordPress admin dashboard. Locate 'Yasglobal Permalinks Customizer' or 'Yas Global Team Permalinks Customizer' and read the version number displayed below the plugin name.
    Affected if The version listed is 2.8.2 or lower.
  2. Verify plugin is active
    In the same Plugins admin page, confirm the plugin shows as 'Active' rather than 'Inactive' or 'Must Use'.
    Affected if The plugin is active and the version is 2.8.2 or lower.
  3. Check plugin file header for version
    Access the plugin directory via FTP or file manager. Open the main plugin PHP file (typically permalinks-customizer.php or similar) and locate the 'Version' header in the plugin comment block.
    Affected if The version in the file header reads 2.8.2 or lower.
  4. Inspect stored permalink settings for suspicious content
    Navigate to the plugin settings page (usually under Settings > Permalinks Customizer). Review any custom permalink fields for unexpected script tags, HTML, or JavaScript code that was not intentionally added.
    Affected if Unexpected script tags, event handlers, or JavaScript code is present in stored permalink configuration fields.
  5. Review page source for injected scripts
    Visit pages on the site using the browser developer tools. View the page source and search for any script tags or event handlers (onload, onerror, onmouseover, etc.) that correspond to user-supplied permalink fields.
    Affected if Malicious JavaScript code appears in rendered pages originating from the plugin's stored settings.

You are affected if the Yas Global Permalinks Customizer plugin is active at version 2.8.2 or lower, as this version contains the stored XSS vulnerability that allows authenticated users to inject malicious scripts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.8.2
Interim mitigation

Update the plugin to a version newer than 2.8.2. If no patched version is available, disable the plugin until a fix is released.

Fix this in Permalinks Customizer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47773 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-47773 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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