Skip to main content

Woffice EUVDEUVD-2026-93256

| CVE-2026-39747 HIGH
SQL Injection (CWE-89)
2026-10-06 Patchstack GHSA-r68f-37wm-v5h4
8.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register or obtain Subscriber account
  2. Exploit
    Send crafted request with SQL payload
  3. Execution
    Injection executed in backend query
  4. Impact
    Exfiltrate database contents (credentials, member data)

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated Subscriber-level account on the target WordPress site (per PR:L and the 'Subscriber SQL Injection' description) and the site must run the Woffice theme at version 5.4.35 or earlier. The practical limiting factor is account access: on sites with open/self-registration enabled - common for Woffice's intranet/membership use case - this barrier is minimal, whereas on sites that disable public registration an attacker needs an existing or granted low-privilege account. No user interaction is needed (UI:N) and the attack is remote over the network (AV:N). The exact vulnerable feature, parameter, or endpoint is not specified in the provided data and must be confirmed from the Patchstack advisory.

Impact

This is an authenticated SQL injection (CWE-89) in the Woffice WordPress theme at versions <= 5.4.35. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L) indicates a network-reachable, low-complexity attack requiring only low privileges (PR:L) and no user interaction, yielding a base score of 8.5 - elevated by the scope change (S:C) and high confidentiality impact. The critical real-world qualifier, confirmed by both the description and PR:L, is that the attacker must hold a Subscriber-level account, the lowest authenticated WordPress role. On sites that allow open user registration (common for Woffice, which is an intranet/community theme built around member accounts), obtaining a Subscriber account is trivial, effectively lowering the barrier close to unauthenticated. No EPSS score, CISA KEV listing, or POC was provided in the input, so there is no public evidence of active exploitation or available exploit code; the risk signal here rests on severity and the low privilege prerequisite rather than demonstrated in-the-wild activity. Note a signal to verify: Patchstack's vector asserts S:C (scope change) and A:L (low availability impact), which are atypical for a read-oriented SQL injection - a standard SQLi usually maps to S:U with no availability impact - so the scope/availability metrics should be confirmed against the full vendor advisory. Net assessment: a genuinely serious, patchable flaw that should be prioritized where self-registration is enabled, but not an emergency without exploitation evidence.

Exploit ScenarioDerived

An attacker registers (or is granted) a low-privilege Subscriber account on a WordPress site running the Woffice theme at version 5.4.35 or earlier, then sends a crafted request to the vulnerable endpoint with malicious SQL in a parameter. Because the input is concatenated into a database query, the attacker extracts sensitive data such as user credentials, session tokens, or private member content. No public exploit code or active exploitation was identified in the provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 06, 2026

Authenticated SQL injection in the Woffice WordPress theme at versions 5.4.35 and earlier lets any Subscriber-level account supply crafted input through an as-yet-unidentified theme endpoint and read arbitrary data from the site's database, including wp_users credential material and any other records the database account can reach. Exploitation is remote (AV:N) and requires no user interaction (UI:N), but does require a valid low-privilege account (PR:L) - a barrier that is minimal on the intranet, membership and community sites Woffice targets, where open self-registration is common. Patchstack reports an 8.5 score, while our independent assessment rates it 6.5 (scope-unchanged, confidentiality-only, no integrity or availability impact); there is no CISA KEV listing and no public exploit identified at time of analysis, and the exact vulnerable parameter must be confirmed from the Patchstack advisory.

RemediationAI

No vendor-released patch identified at time of analysis - the provided data contains no fix version and no patch reference, so the first step is to check the Patchstack advisory (https://patchstack.com/database/wordpress/theme/woffice/vulnerability/wordpress-woffice-theme-5-4-35-sql-injection-vulnerability?_s_id=cve) and the Woffice changelog for a release above 5.4.35 and upgrade to it as soon as one is published; until then, treat the theme as unfixed. The most effective compensating control is to close the account-access prerequisite: disable public/self-registration (WordPress Settings > General > Membership) so no new Subscriber accounts can be created, and audit and remove or downgrade existing Subscriber accounts that are not trusted users - the trade-off is that this breaks the self-service onboarding that intranet and membership sites depend on, so pair it with an administrator-provisioned account process if the site needs one. If registration must stay open, add a managed WAF or reverse-proxy rule set that inspects theme AJAX/admin-ajax and REST requests for SQL metacharacters and UNION/boolean patterns, accepting the known costs of signature false positives and the fact that this is bypassable and not a remedy. Additionally, restrict the WordPress database user's privileges so it cannot read tables outside the wp_ schema (limiting what any successful injection can exfiltrate), and monitor for anomalous query behaviour or unexpected SELECT activity against wp_users, since with a confidentiality-only impact the exploitation signature is data access rather than file or content modification. Rotating WordPress salts and forcing a password reset for all users is worth doing if you suspect the site was already probed, given the potential exposure of password hashes.

Affected VersionsENISA

Woffice n/a ≤5.4.35

Affected Packages

euvd woffice no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Woffice is a commercial multipurpose WordPress theme from WofficeIO aimed at intranets, extranets and membership/community portals, and the flaw is a classic CWE-89 SQL injection in its PHP code. WordPress themes run with the full privileges of the site's database user, and theme code that builds SQL by string concatenation - rather than using $wpdb->prepare() with placeholders, or the WordPress REST/query APIs - lets user-controlled input reach the query text unescaped. The CPE cpe:2.3:a:wofficeio:woffice:*:*:*:*:*:*:*:* carries a wildcard version, so the only version boundary the vendor data gives is the advisory's '<= 5.4.35' ceiling; every release up to and including 5.4.35 should be treated as affected. The access prerequisite is the interesting part: the 'Subscriber SQL Injection' designation and the PR:L vector indicate the injectable code path is reachable by the lowest default WordPress role, which normally can only manage its own profile and read published content - so a feature such as a profile field, front-end submission handler or AJAX action is likely being queried against the database without capability checks on the data it accepts. Our assessment scores this as scope-unchanged with high confidentiality impact and no integrity or availability impact, meaning the realistic outcome is data exfiltration (potentially including password hashes cracked offline) rather than database modification or denial of service, and the vendor's 8.5 figure reflects a scope-changed, A:L reading that we do not adopt.

Know when Woffice gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 8.5 HIGH
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
vuln.today AI 6.5 MEDIUM

Remote, low-complexity injection needing only a Subscriber account (PR:L); full database read gives C:H, while a read-oriented SQLi keeps S:U with no integrity or availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

DescriptionCVE.org

Subscriber SQL Injection in Woffice <= 5.4.35 versions.

Executive ViewAI

Why It Matters

The Woffice WordPress theme (versions 5.4.35 and earlier) contains a high-severity SQL injection vulnerability that allows any authenticated Subscriber-level user to read sensitive database contents, including user credentials. Organizations running this theme on intranet, membership, or community sites-where self-registration is often enabled-face a heightened risk of data exposure because attackers can easily obtain low-privilege accounts. With no vendor patch currently available, leadership should prioritize interim mitigations to protect user data and maintain trust.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: restrict or disable open registration to limit Subscriber account creation; enforce least privilege on the database account; deploy WAF rules to detect and block SQL injection patterns; monitor logs for unusual database queries from low-privilege users; consider temporarily deactivating the Woffice theme if feasible.

Threat Intelligence Overview

EPSS Score
0.3%
Top 74% exploitable
Prevalence
Medium
popular commercial WordPress intranet/community theme, moderate deployment footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

CVE-2025-2798 CRITICAL
9.8 Apr 04

The Woffice CRM theme for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 5.4.21.

CVE-2024-43153 CRITICAL
9.8 Aug 13

Incorrect Privilege Assignment vulnerability in WofficeIO Woffice woffice.4.10. Rated critical severity (CVSS 9.8), this

CVE-2024-43234 CRITICAL
9.8 Dec 16

Authentication Bypass Using an Alternate Path or Channel vulnerability in WofficeIO Woffice woffice allows Authenticatio

CVE-2024-37470 CRITICAL
9.8 Nov 01

Missing Authorization vulnerability in WofficeIO Woffice Core allows Accessing Functionality Not Properly Constrained by

CVE-2025-2780 HIGH
8.8 Apr 04

The Woffice Core plugin for WordPress, used by the Woffice Theme, is vulnerable to arbitrary file uploads due to missing

CVE-2024-37472 HIGH
7.1 Jul 04

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WofficeIO Woffice

CVE-2024-37471 MEDIUM
6.1 Jul 04

Cross Site Scripting (XSS) vulnerability in WofficeIO Woffice Core allows Reflected XSS.4.8. Rated medium severity (CVSS

CVE-2025-2797 MEDIUM
5.4 Apr 04

The Woffice Core plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including,

CVE-2026-27435 MEDIUM
5.3 Jul 01

Broken access control in the WofficeIO Woffice WordPress theme (all versions before 5.4.33) permits unauthenticated remo

CVE-2025-7694 MEDIUM
6.8 Aug 02

The Woffice Core plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy