dbcve.org
Ht PoliticWordPress extension · Hasthemes

CVE-2024-51673

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-09
Fix available
A fix is available. Upgrade to 2.4.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 DevItems HT Politic wp-politic allows DOM-Based XSS.This issue affects HT Politic: from n/a through <= 2.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 confidence

DOM-based Cross-site Scripting (XSS) vulnerability in the HT Politic WordPress theme allows attackers to inject malicious JavaScript through user-controlled input that is dynamically processed in the browser's DOM without proper sanitization or output encoding.

MitigationFix the vulnerable JavaScript code to properly sanitize and encode user input before rendering it in the DOM; implement Content Security Policy (CSP) headers as defense-in-depth.

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
Ht PoliticWordPress extension
Affected:< 2.4.5

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm HT Politic theme is installed
    Navigate to WordPress admin Appearance > Themes or inspect /wp-content/themes/ directory for a folder named 'ht-politic' or similar
    Affected if The theme folder exists in the WordPress themes directory
  2. Identify installed theme version
    Open the theme's style.css file in /wp-content/themes/ht-politic/ and locate the 'Version:' header in the file comments
    Affected if Version number is lower than 2.4.5 or version header is missing entirely
  3. Locate JavaScript files handling DOM manipulation
    Inspect all .js files in the /wp-content/themes/ht-politic/ directory, focusing on files that contain DOM manipulation methods such as innerHTML, outerHTML, insertAdjacentHTML, document.write, or jQuery methods that modify the DOM
    Affected if JavaScript files exist that process and render user input directly into the DOM without sanitization
  4. Identify user-controlled input sinks in the vulnerable code
    Search the JavaScript files for patterns where URL parameters (such as window.location.search, URLSearchParams), form inputs, or stored data are passed to innerHTML, $(...).html(), or similar DOM-setter methods without using a sanitization function
    Affected if Code passes raw user input to DOM-setter methods without encoding or sanitization

The environment is affected if the HT Politic theme is installed with a version lower than 2.4.5 and contains JavaScript code that renders unsanitized user input into the browser DOM.

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
Upgrade available Upgrade to 2.4.5 or later
Fixed in 2.4.5
Interim mitigation

Fix the vulnerable JavaScript code to properly sanitize and encode user input before rendering it in the DOM; implement Content Security Policy (CSP) headers as defense-in-depth.

Recommended fix High confidence

HT Politic version 2.4.5

  1. 1. Create a complete backup of your WordPress site (database and files) before making any changes.
  2. 2. Log in to the WordPress admin dashboard.
  3. 3. Navigate to Appearance > Themes.
  4. 4. Locate the HT Politic theme and verify the current version is 2.4.4 or lower.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 2.4.5.
  6. 6. If no automatic update appears, manually download HT Politic version 2.4.5 from the official WordPress theme repository or a trusted source.
  7. 7. To manually update: go to Appearance > Themes, delete the old HT Politic theme, then upload and activate version 2.4.5.
  8. 8. After updating, clear any caching plugins and test the site to ensure the theme functions correctly.
Caveat Standard risk applies with any theme update; custom child theme modifications may require review after upgrade

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

Fix this in Ht Politic Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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