Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in ovatheme Cube Portfolio cubeportfolio allows SQL Injection.This issue affects Cube Portfolio: from n/a through <= 1.16.8.
Security readout for executives and security teams
Plain-English summary
CVE-2025-52823 is a high-severity SQL injection issue in the WordPress Cube Portfolio plugin up to version 1.16.8. A low-privileged authenticated user may be able to trigger database queries that expose sensitive data and affect availability.
Executive priority
Treat as a priority remediation item for affected WordPress sites because database exposure is the main business risk. Prioritize internet-facing sites with user registration or many non-admin accounts.
Technical view
The CVE describes CWE-89 improper neutralization in ovatheme Cube Portfolio. CVSS 3.1 is 8.5 with network access, low attack complexity, low privileges required, no user interaction, changed scope, high confidentiality impact, and low availability impact.
Likely exposure
Exposure is limited to WordPress sites using the Cube Portfolio plugin at version 1.16.8 or earlier. The CVSS vector indicates attacker privileges are required, so public registration and low-privilege accounts matter.
Exploitation context
The provided bundle does not show CISA KEV listing or confirmed active exploitation. It also does not provide exploit details, proof-of-concept status, or a named fixed version.
Researcher notes
Evidence is limited to the CVE record and Patchstack entry. Affected-version metadata in the bundle is sparse, so validate directly against installed Cube Portfolio versions and vendor advisories before declaring exposure closed.
Mitigation direction
Inventory WordPress sites for Cube Portfolio plugin installations.
Confirm whether any installation is version 1.16.8 or earlier.
Check vendor and Patchstack guidance for a fixed release or official mitigation.
Disable or remove the plugin where it is unnecessary.
Reduce access for low-privilege WordPress accounts until remediated.
Validation and detection
Verify installed plugin versions from WordPress administration or asset inventory.
Review whether subscriber or contributor accounts exist on affected sites.
Check web and application logs for unusual database errors or plugin requests.
Confirm remediation by rechecking the plugin version or removal state.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.