Security readout for executives and security teams
Plain-English summary
A WordPress forum plugin flaw can let an unauthenticated attacker query database information through vulnerable topic sorting behavior. The main business risk is exposure of WordPress user credential data or other sensitive database records on sites running affected wpForo Forum versions.
Executive priority
Prioritize remediation for internet-facing WordPress sites because exploitation requires no login and may expose credential data. This is high urgency for sites with active forums, customer accounts, or privileged WordPress users.
Technical view
CVE-2026-28562 is a CWE-89 SQL injection in wpForo Forum Topics::get_topics(). The source bundle attributes the issue to unsafe ORDER BY handling where esc_sql() is ineffective for unquoted identifiers. CVSS v4.0 is 8.8, with network access, no privileges, and no user interaction required.
Likely exposure
Exposure is most likely for public WordPress sites running wpForo Forum versions identified in the bundle, especially 2.4.14. The bundle also lists 2.4 and 2.4.15 as affected, so confirm exact installed versions against vendor and CVE records.
Exploitation context
The bundle describes blind boolean SQL injection and potential credential extraction from the WordPress database. It does not cite CISA KEV listing or confirmed active exploitation in the wild, so treat exploitation as plausible but not confirmed from these sources.
Researcher notes
Evidence is strong for vulnerability class, affected component, and severity from the provided CVE and VulnCheck references. Evidence is incomplete on observed exploitation and the exact fixed version, so do not assert active exploitation or a specific patch level without vendor confirmation.
Mitigation direction
- Inventory WordPress sites using wpForo Forum and record exact plugin versions.
- Check the WordPress.org developer changelog and vendor guidance for the fixed release.
- Update affected wpForo Forum installations according to vendor guidance.
- Restrict unnecessary public access to forum functionality where business requirements allow.
- Review database and WordPress account activity for suspicious access patterns.
Validation and detection
- Confirm whether wpForo Forum is installed on each WordPress site.
- Compare installed versions with the CVE record, VulnCheck advisory, and vendor changelog.
- Check web server and application logs for unusual topic sorting requests.
- Verify the plugin update completed successfully in WordPress administration.
- Review WordPress users for unexpected administrator accounts or password reset activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupDatabase behavior lookup
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.
Open ATT&CK lookupCVE-2026-28562 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N3.94.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.8HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- wpForo Forum WordPress PluginCVE reference, VulnCheck · product, patch
- VulnCheck Advisory: wpForo 2.4.14 SQL Injection via Topics ORDER BY ParameterCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.