Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Theme security history

Besa - Elementor Marketplace WooCommerce Theme Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 3 vulnerability records associated with Besa - Elementor Marketplace WooCommerce Theme, published between 2025 and 2026.

Dataset last synchronized: 2026-08-03 00:31:25 UTC

At a glance

Security Snapshot

3Total records
1Critical
2High
0Medium
0Low
0Informational
3Patched records
0Currently marked unpatched
2025-06-11First disclosure
2026-02-04Latest disclosure
3 of 3CVE coverage

Use this history

Check and watch Besa - Elementor Marketplace WooCommerce Theme.

A history record does not establish whether the version installed on your website is affected. Enter the exact version in the checker, or add this software to a private Critical/High alert watchlist.

Year-by-Year Timeline

YearRecordsRelative volume
202522 records
202611 records

Severity Breakdown

SeverityRecordsShare
Critical133.3%
High266.7%

Vulnerability-Type Breakdown

Other

3 records100%

First: 2025. Latest: 2026.

Patch Status

Patched
3
Currently marked unpatched
0
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

  • 2.3.16
  • 2.3.10

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-2.3.15Besa <= 2.3.15 - Unauthenticated Local File InclusionFebruary 4, 20262.3.16High
*-2.3.15Besa <= 2.3.15 - Authenticated (Contributor+) Local File InclusionDecember 15, 20252.3.16High
*-2.3.8Besa <= 2.3.8 - Unauthenticated Local File InclusionJune 11, 20252.3.10Critical

Selected source records

Latest Records

HighCVE-2025-67981

Besa <= 2.3.15 - Unauthenticated Local File Inclusion

Published: February 4, 2026

Affected versions
*-2.3.15
Patched versions
2.3.16
Original Wordfence record
HighCVE-2025-67530

Besa <= 2.3.15 - Authenticated (Contributor+) Local File Inclusion

Published: December 15, 2025

Affected versions
*-2.3.15
Patched versions
2.3.16
Original Wordfence record
CriticalCVE-2025-49252

Besa <= 2.3.8 - Unauthenticated Local File Inclusion

Published: June 11, 2025

Affected versions
*-2.3.8
Patched versions
2.3.10
Original Wordfence record

Highest-Severity Records

CriticalCVE-2025-49252

Besa <= 2.3.8 - Unauthenticated Local File Inclusion

Published: June 11, 2025

Affected versions
*-2.3.8
Patched versions
2.3.10
Original Wordfence record
HighCVE-2025-67981

Besa <= 2.3.15 - Unauthenticated Local File Inclusion

Published: February 4, 2026

Affected versions
*-2.3.15
Patched versions
2.3.16
Original Wordfence record
HighCVE-2025-67530

Besa <= 2.3.15 - Authenticated (Contributor+) Local File Inclusion

Published: December 15, 2025

Affected versions
*-2.3.15
Patched versions
2.3.16
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory