Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain Subscriber account
-
ExploitSend crafted request with SQL payload
-
ExecutionInjection executed in backend query
-
ImpactExfiltrate 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber SQL Injection in Woffice <= 5.4.35 versions.
Executive ViewAI
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.
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
The Woffice CRM theme for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 5.4.21.
Incorrect Privilege Assignment vulnerability in WofficeIO Woffice woffice.4.10. Rated critical severity (CVSS 9.8), this
Authentication Bypass Using an Alternate Path or Channel vulnerability in WofficeIO Woffice woffice allows Authenticatio
Missing Authorization vulnerability in WofficeIO Woffice Core allows Accessing Functionality Not Properly Constrained by
The Woffice Core plugin for WordPress, used by the Woffice Theme, is vulnerable to arbitrary file uploads due to missing
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WofficeIO Woffice
Cross Site Scripting (XSS) vulnerability in WofficeIO Woffice Core allows Reflected XSS.4.8. Rated medium severity (CVSS
The Woffice Core plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including,
Broken access control in the WofficeIO Woffice WordPress theme (all versions before 5.4.33) permits unauthenticated remo
The Woffice Core plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation
EUVD-2026-93256
GHSA-r68f-37wm-v5h4
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB