dbcve.org
AttorneyWordPress extension · Hennessey

CVE-2023-41692

MEDIUM · 6.1 CVSS v3.1 Published 2023-10-02
Fix available
A fix is available. Upgrade to after 3 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
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Hennessey Digital Attorney theme <= 3 theme.

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

An unauthenticated reflected cross-site scripting (XSS) vulnerability exists in the Hennessey Digital Attorney WordPress theme version 3 and below, where user-supplied input is not properly sanitized or escaped before being reflected back in the HTTP response, allowing injection of arbitrary JavaScript code.

MitigationUpdate the Hennessey Digital Attorney theme to a version newer than 3, or implement proper input validation and output encoding for all user-supplied parameters in the affected theme code.

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
AttorneyWordPress extension
Affected:<= 3

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. Verify Hennessey Attorney theme is installed
    Check the WordPress themes directory (wp-content/themes/) for a folder named 'hennessey-attorney', 'hennessey-digital-attorney', or similar naming pattern. Log into WordPress admin and navigate to Appearance > Themes to list all installed themes.
    Affected if The Hennessey Digital Attorney theme or any variant with 'hennessey' and 'attorney' in the name appears in the installed themes list
  2. Determine the installed theme version
    Open the theme's style.css file located in the theme folder and look for the 'Version:' declaration in the file header comment. Alternatively, in WordPress admin, click on the theme to view its details including version number.
    Affected if The reported version is 3 or lower, or if no version is displayed and the theme matches the affected product name
  3. Identify vulnerable parameter handling code
    Search the theme files (particularly PHP files in the theme root and includes subdirectories) for patterns where user input from $_GET, $_POST, or $_REQUEST is directly output without sanitization functions such as esc_html(), esc_attr(), or wp_kses(). Look for echoed variables that contain request parameters.
    Affected if Code is found that reflects $_GET, $_POST, or $_REQUEST parameters directly into HTML output without using WordPress sanitization functions like esc_html() or esc_attr()
  4. Confirm the theme is active on a live site
    In WordPress admin, check which theme is currently activated under Appearance > Themes. For network/multisite installs, check each site's active theme. If the site is publicly accessible, the theme CSS and response headers may reveal the active theme.
    Affected if The Hennessey Attorney theme version 3 or lower is currently activated and serving pages to visitors

If the Hennessey Digital Attorney theme version 3 or lower is installed and actively in use on the WordPress site, the environment is affected by this reflected XSS vulnerability.

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 3
Interim mitigation

Update the Hennessey Digital Attorney theme to a version newer than 3, or implement proper input validation and output encoding for all user-supplied parameters in the affected theme code.

Fix this in Attorney Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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