dbcve.org
WofficeWordPress extension · Xtendify

CVE-2024-37471

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-04
Fix available
A fix is available. Upgrade to 5.4.9 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
Cross Site Scripting (XSS) vulnerability in WofficeIO Woffice Core allows Reflected XSS.This issue affects Woffice Core: from n/a through 5.4.8.

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

Reflected XSS vulnerability in Woffice Core allows attackers to inject malicious scripts via unsanitized user input that gets reflected back in the HTTP response. The vulnerability exists in versions up to and including 5.4.8.

MitigationUpdate Woffice Core to the latest patched version. If no patch is available, implement input validation and output encoding on all user-supplied parameters before reflecting them in responses.

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
WofficeWordPress extension
Affected:< 5.4.9

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. Identify installed Woffice version
    Locate the Woffice Core version file. Common paths include: /wp-content/themes/woffice/style.css (check 'Version:' field), or check the WordPress plugin/theme admin page under Appearance > Themes, or query the database if accessible. Look for a 'Version' constant in core files.
    Affected if The installed version is 5.4.8 or lower (any version < 5.4.9).
  2. Confirm Woffice Core is active
    Verify the Woffice theme or plugin is actively installed and running on the WordPress site. Check via WordPress admin dashboard under Appearance > Themes or Plugins, or inspect page source for Woffice-specific CSS/JS paths.
    Affected if Woffice Core is the active theme or plugin and the version cannot be determined or is confirmed < 5.4.9.
  3. Identify endpoints that reflect user input
    Review application pages and identify URL parameters that display user-supplied values in the HTTP response (such as search parameters, form submissions, or query strings). Common locations include search bars, filter parameters, and URL redirect parameters.
    Affected if The application reflects any user-supplied GET or POST parameters directly in HTML output without visible sanitization.
  4. Test for reflected XSS via parameter injection
    Using a browser or HTTP tool, submit a benign test payload (such as <script>alert(1)</script> or an encoded variant) as a URL parameter on pages that reflect input. Observe if the payload executes or appears unescaped in the page source.
    Affected if The payload is reflected verbatim in the response (visible in page source or rendered) without HTML encoding, indicating lack of output sanitization.
  5. Check current input sanitization practices
    Inspect the application code handling the reflected parameters. Look for functions like htmlspecialchars(), esc_html(), or WordPress sanitization functions in the code that processes the relevant input and outputs it to response.
    Affected if No sanitization functions are found in the code path handling reflected parameters, or the code directly outputs user input without transformation.

A user is affected if Woffice Core version is below 5.4.9 AND the application reflects user-supplied parameters in HTTP responses without proper output encoding.

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 5.4.9 or later
Fixed in 5.4.9
Interim mitigation

Update Woffice Core to the latest patched version. If no patch is available, implement input validation and output encoding on all user-supplied parameters before reflecting them in responses.

Recommended fix High confidence

5.4.9

  1. 1. Backup your WordPress site before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins or Theme section depending on how Woffice is installed.
  4. 4. Locate Woffice and check the current version is below 5.4.9.
  5. 5. Update Woffice to version 5.4.9 or later.
  6. 6. Verify the update was successful by checking the version number.
  7. 7. Test the affected functionality to confirm the XSS vulnerability is remediated.

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

Fix this in Woffice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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