LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68045: WordPress WP Event SOlution plugin <= 4.1.12 - Broken Access Control vulnerability

Unauthenticated Broken Access Control in WP Event SOlution <= 4.1.12 versions.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-68045 affects the WordPress WP Event SOlution plugin through version 4.1.12. An unauthenticated attacker may access protected information because access controls are missing or insufficient. The business concern is potential exposure of confidential event or site data on affected WordPress sites.

Executive priority

Prioritize affected public WordPress sites, especially those handling attendee, customer, or private event data. Treat as urgent remediation, but not confirmed emergency exploitation based on the provided sources.

Technical view

The issue is CWE-862, Missing Authorization, in Arraytics WP Event SOlution for WordPress. CVSS 3.1 is 7.5 high: network exploitable, low complexity, no privileges, no user interaction, with high confidentiality impact and no stated integrity or availability impact.

Likely exposure

Exposure is limited to WordPress sites running WP Event SOlution version 4.1.12 or earlier. The source bundle does not identify affected endpoints, data types, or a fixed version.

Exploitation context

The CVE is not listed as KEV in the provided data, and no cited source states active exploitation. The attack requirements are low because exploitation is unauthenticated and network-accessible, but public exploit status is not established here.

Researcher notes

The public details are sparse. The CVE and Patchstack entry identify unauthenticated broken access control, but do not provide endpoint details, proof-of-concept status, or a named fixed version in the supplied bundle.

Mitigation direction

  • Inventory WordPress sites for WP Event SOlution installations and versions.
  • If running 4.1.12 or earlier, check vendor and Patchstack guidance immediately.
  • Update if a fixed release is available from the plugin vendor.
  • Disable or remove the plugin where it is not business-critical.
  • Restrict access to sensitive event-related data until resolved.

Validation and detection

  • Confirm whether WP Event SOlution is installed on each WordPress site.
  • Record the installed plugin version and compare it to 4.1.12.
  • Review vendor, WordPress, and Patchstack pages for fixed-version guidance.
  • Check web server logs for unusual unauthenticated access to plugin-related resources.
  • Verify compensating controls do not break event site functionality.
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 · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-68045 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
7.5 (3.1)
Known Exploited
No
Published

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

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
3Timeline 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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ArrayticsWP Event SOlutionwp-event-solution, n/aunaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.