Woffice - Security Vulnerability (CVE-2026-39747)
CVE-2026-39747
Subscriber SQL Injection in Woffice
CVE-2026-39747
CVE-2026-39747
Subscriber SQL Injection in Woffice
CVE-2026-39747
Machine-generated threat intelligence
AI Updated 6 days ago
AI enriched 6 days ago (2026-10-11 00:35 UTC)
Subscriber SQL Injection in Woffice
Severity is HIGH (CVSS 8.5). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.
Exploitability is assessed as High based on severity and technical exposure profile.
Primary risk drivers: severity and technical exposure profile
Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.
Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.
AI risk score 76/100 (High, High) with priority P2 Urgent. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.
Patch promptly The consequence is significant even where an attacker needs a foothold first.
Update Woffice to the latest available version.
Where the vendor has not published a fix yet, disable the plugin until they do.
Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.
Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.
Scan your site to see whether it runs Woffice, and at which version.
Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.
You are affected if your site runs Woffice.
Update Woffice to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.
This is a SQL Injection flaw. An attacker who exploits it can read, alter or delete anything in the site database, including user accounts and password hashes.