dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-50533

HIGH · 7.1 CVSS v3.1 Published 2024-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Cross-Site Request Forgery (CSRF) vulnerability in David Garcia Domain Sharding domain-sharding allows Stored XSS.This issue affects Domain Sharding: from n/a through <= 1.2.1.

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 confidence

A CSRF vulnerability in the Domain Sharding plugin <= 1.2.1 allows attackers to craft malicious requests that inject and persistently store XSS payloads into the application. When other users subsequently view affected pages, the stored XSS payloads execute in their browsers.

MitigationImplement anti-CSRF tokens (synchronizer tokens) on all state-changing endpoints and apply proper input validation and output encoding to prevent XSS injection.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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. Verify Domain Sharding plugin is installed
    Check your CMS/plugin inventory or file system for the Domain Sharding plugin component. Common locations include wp-content/plugins/ (WordPress), sites/all/modules/ (Drupal), or similar plugin directories for other platforms.
    Affected if The Domain Sharding plugin is present in the installation
  2. Confirm the installed version number
    Locate the plugin's version metadata (typically in a version.php, plugin.json, readme.txt, or main plugin header) and compare it to the affected range: any version <= 1.2.1
    Affected if The installed version is 1.2.1 or lower
  3. Identify state-changing endpoints
    Review application routing or plugin code to find endpoints that handle Domain Sharding configuration changes (e.g., save, update, add, delete operations for sharding settings).
    Affected if The plugin exposes endpoints that modify domain sharding configuration without requiring CSRF validation
  4. Inspect stored data for XSS payloads
    Query the database or configuration storage for any domain/sharding-related records containing suspicious JavaScript tags, event handlers, or encoded payloads (e.g., <script>, onerror=, onload=, javascript:).
    Affected if Stored XSS payloads exist in domain sharding configuration data that would render in user browsers
  5. Check CSRF token enforcement
    Review the plugin's form handlers and API endpoints to verify whether anti-CSRF tokens (synchronizer tokens) are validated on all state-changing operations.
    Affected if State-changing endpoints lack CSRF token validation

A user is affected if the Domain Sharding plugin version is 1.2.1 or lower AND the plugin processes configuration changes without CSRF protection, allowing injection of persistent XSS payloads.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (synchronizer tokens) on all state-changing endpoints and apply proper input validation and output encoding to prevent XSS injection.

Recommended fix Moderate confidence

Latest version of Domain Sharding plugin (check WordPress plugin repository for post-1.2.1 security release)

  1. Check the WordPress plugin repository or contact the plugin developer (David Garcia) to obtain the fixed version of the Domain Sharding plugin
  2. Locate the specific security release that addresses CVE-2024-50533
  3. Update the Domain Sharding plugin to the latest version available
  4. Verify the update was successful and test that the plugin functions correctly
  5. Consider implementing additional CSRF protections in WordPress using nonce tokens for admin actions as a defense-in-depth measure
Caveat Review plugin changelog for any breaking changes between 1.2.1 and the fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-50533 — 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-2024-50533 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