# CVE-2026-39747: WordPress Woffice theme < 5.4.43 - SQL Injection vulnerability

Status: published. Published: 2026-10-06. Updated: 2026-11-05.

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WofficeIO Woffice woffice allows SQL Injection.This issue affects Woffice: from n/a before 5.4.43.

## Remediation

- fix: Update the WordPress Woffice theme to the latest available version (at least 5.4.43). (source: CNA: Patchstack)

## Affected products and versions

- WofficeIO / Woffice (woffice): ≥ 0; < 5.4.43 (affected, custom); unaffected at 5.4.43. Source: CNA: Patchstack

## Severity and prioritization

- CVSS 3.1: 8.5 (high); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L; source: CNA: Patchstack

- CISA KEV: No listing in collected sources

- EPSS: 0.33% as of 2026-11-04; percentile 26.58%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: CWE-89

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://patchstack.com/database/wordpress/theme/woffice/vulnerability/wordpress-woffice-theme-5-4-35-sql-injection-vulnerability?_s_id=cve (CNA: Patchstack; vdb-entry)

## Provenance

- CNA: Patchstack: https://www.cve.org/CVERecord?id=CVE-2026-39747; retrieved 2026-11-05; source updated 2026-11-05

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-39747; retrieved 2026-11-05; source updated Not reported

Revision: d9cdd4cc1d56f5c9d37d428021a4762393b8746b45a221c96c063ed95f4499f2

Canonical: https://y2.dev/cve/CVE-2026-39747

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.