LiveActive security incident?Get immediate response
CVE Record

CVE-2025-54031: WordPress Support Board <= 3.8.0 - Local File Inclusion Vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Schiocco Support Board supportboard allows PHP Local File Inclusion.This issue affects Support Board: from n/a through <= 3.8.0.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-54031 affects the WordPress Support Board plugin through version 3.8.0. A flaw in how PHP files are included may let an unauthenticated attacker reach local file inclusion behavior, with possible confidentiality, integrity, and availability impact. The available sources do not name a fixed version or active exploitation.

Executive priority

High priority for organizations running this plugin, especially on public WordPress sites. The business risk is meaningful because the rated impact is high across data exposure, tampering, and service disruption, while remediation guidance in the supplied sources is incomplete.

Technical view

The issue is classified as CWE-98: improper control of filenames used in PHP include/require statements. The CVSS 3.1 score is 8.1, with network access, no privileges, no user interaction, high attack complexity, and high CIA impact. Public details are sparse beyond Patchstack/CVE metadata.

Likely exposure

Exposure is likely limited to WordPress sites using Schiocco Support Board, supportboard, at versions up to and including 3.8.0. The bundle provides no CPEs and marks default status unaffected, so asset validation is required.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no provided source states active exploitation. Attack complexity is rated high, but successful abuse could have severe impact. Treat exploitation status as unconfirmed, not absent.

Researcher notes

Public metadata identifies LFI through improper PHP include/require filename handling, but does not provide affected code paths, proofs of concept, exploit telemetry, or a fixed version. Avoid assuming exploitability details beyond the CVSS vector and Patchstack/CVE classification.

Mitigation direction

  • Inventory WordPress sites for Support Board installations and versions.
  • Prioritize any instance running Support Board through version 3.8.0.
  • Check Schiocco and Patchstack guidance for a fixed release or workaround.
  • Disable or isolate affected deployments if no official fix is available.
  • Monitor web and PHP logs for suspicious include-related errors.

Validation and detection

  • Confirm whether Support Board is installed on each WordPress site.
  • Record exact plugin versions and flag versions up to 3.8.0.
  • Review vendor and Patchstack pages for current remediation guidance.
  • Check change records for plugin updates or temporary disablement.
  • Look for anomalous file access or PHP include warnings in logs.
Prepared
Confidence
medium
Sources
3

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 · low confidence lookup

CWE-98: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2025-54031 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2025-54031Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SchioccoSupport Boardsupportboard, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-98 · source CWE mapping

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.