LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25135: vBulletin before 5.6.9 PL1 allows an unauthenticated remote attacker to execute arbitrary code via a crafte...

vBulletin before 5.6.9 PL1 allows an unauthenticated remote attacker to execute arbitrary code via a crafted HTTP request that triggers deserialization. This occurs because verify_serialized checks that a value is serialized by calling unserialize and then checking for errors. The fixed versions are 5.6.7 PL1, 5.6.8 PL1, and 5.6.9 PL1.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-25135 is a critical vBulletin flaw that can let an unauthenticated remote attacker run code through a crafted HTTP request. For a business, an exposed vulnerable forum can become a full server compromise risk, not just a website defacement issue.

Executive priority

Treat this as urgent for any internet-facing vBulletin deployment. The vulnerability has full confidentiality, integrity, and availability impact, and it requires no login or user action. Patch verification should be tracked to completion.

Technical view

The issue is CWE-502 unsafe deserialization in vBulletin before the listed PL1 fixes. The vulnerable verify_serialized logic checks serialized input by calling unserialize and then inspecting errors, creating a remote code execution condition reachable without authentication.

Likely exposure

Exposure is most likely on internet-facing vBulletin 5 sites not updated to 5.6.7 PL1, 5.6.8 PL1, or 5.6.9 PL1. The bundle does not provide CPEs or a full affected-version matrix.

Exploitation context

The CVSS 3.1 score is 9.8 with network access, low complexity, no privileges, and no user interaction. The provided bundle does not show CISA KEV listing or cited evidence of active exploitation.

Researcher notes

Analysis is source-limited. The bundle identifies the root cause, CWE-502, CVSS vector, and fixed PL1 releases, but does not include exploit telemetry, CPEs, or detailed vulnerable configuration prerequisites.

Mitigation direction

  • Upgrade affected vBulletin installations to the vendor-listed PL1 fixed versions.
  • Check the vendor security announcement for branch-specific update guidance.
  • Prioritize public forum instances and systems sharing the same application host.
  • Back up and test the forum before production patching.
  • Retire or isolate any unsupported vBulletin deployments.

Validation and detection

  • Inventory externally reachable vBulletin sites and confirm exact version and patch level.
  • Verify installations report 5.6.7 PL1, 5.6.8 PL1, or 5.6.9 PL1 where applicable.
  • Review web and application logs for unusual unauthenticated request patterns.
  • Confirm patching in staging before production rollout.
  • Document remaining exceptions with owner, exposure, and remediation date.
Prepared
Confidence
medium
Sources
4

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-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-25135 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/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
3Source 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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-25135Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/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
n/an/an/aListed
Weakness

CWE details

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

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.