Tagdiv ComposerWordPress extension · Tagdiv
CVE-2023-39166
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in tagDiv tagDiv Composer allows Cross-Site Scripting (XSS).This issue affects tagDiv Composer: from n/a before 4.4.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability in tagDiv Composer allows attackers to inject malicious JavaScript code by tricking authenticated administrators into submitting crafted requests. The lack of proper CSRF token validation on form submissions enables attackers to perform actions on behalf of victims, leading to stored Cross-Site Scripting (XSS).
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
Tagdiv ComposerWordPress extension
< 4.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed tagDiv Composer versionLocate the version number of tagDiv Composer in your WordPress plugins directory, theme files, or admin dashboard plugin information panelAffected if The version is lower than 4.4 (e.g., 4.3, 4.2, etc.)
-
Verify admin access to tagDiv ComposerLog into the WordPress admin panel and navigate to the tagDiv Composer settings or page builder interfaceAffected if You can access the composer admin interface as an authenticated administrator
-
Locate form submission points in the composerInspect the HTML source of tagDiv Composer admin pages to identify form elements that accept user inputAffected if Forms exist that submit data without visible CSRF token fields
-
Check form submissions for CSRF token validationReview the underlying PHP files handling form submissions in the tagDiv Composer plugin or theme for CSRF token verification logicAffected if Form handlers lack token validation checks (e.g., no wp_verify_nonce or check_admin_referer calls)
-
Determine if input sanitization is presentExamine the same form handling code for output encoding or sanitization functions when storing user inputAffected if User-submitted data is stored without sanitization functions like esc_html, esc_attr, or sanitize_text_field
You are affected if tagDiv Composer version is below 4.4 and the admin forms lack proper CSRF token validation on submissions.
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.
dbcve · scoped4.4
Update tagDiv Composer to version 4.4 or later which includes proper CSRF token validation and input sanitization. Additionally, implement SameSite cookies and verify origin headers on sensitive operations.
4.4
- 1. Backup your WordPress site before making any changes
- 2. Navigate to the WordPress admin dashboard
- 3. Go to Plugins or Theme panel where tagDiv Composer is installed
- 4. Update tagDiv Composer to version 4.4 or later
- 5. Verify the update was successful by checking the installed version
- 6. Test the functionality to ensure the update did not break existing features
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Tagdiv Composer
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39166 — 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-2023-39166 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