LiveActive security incident?Get immediate response
CVE Record

CVE-2025-58955: WordPress Karzo theme < 2.6 - Local File Inclusion vulnerability

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in designervily Karzo karzo allows PHP Local File Inclusion.This issue affects Karzo: from n/a through < 2.6.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in the Karzo WordPress theme (versions up to 2.6) lets an unauthenticated attacker trick the site into loading local files it should not. On a vulnerable WordPress site, this can expose sensitive configuration, credentials, or lead to deeper compromise. Sites using this theme should treat it as a high-priority issue and follow vendor guidance promptly.

Executive priority

High priority for any business running a WordPress site that uses the Karzo theme. Schedule remediation this sprint: confirm exposure, follow vendor guidance, and consider deactivating the theme if a fix is not yet available. Non-Karzo WordPress estates are not directly impacted.

Technical view

CVE-2025-58955 is a Local File Inclusion (CWE-98) in the designervily Karzo theme through version < 2.6. A request-controlled value reaches a PHP include/require without proper validation, allowing inclusion of arbitrary local files. CVSS 3.1 is 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), reflecting unauthenticated network access with high attack complexity but high impact across confidentiality, integrity, and availability.

Likely exposure

Any internet-facing WordPress site running the Karzo theme at a version below 2.6 is potentially exposed. Exposure depends on whether the vulnerable code path is reachable in the deployed theme configuration. No authentication is required, but Patchstack-rated complexity suggests non-trivial conditions.

Exploitation context

Not listed in CISA KEV and no public exploitation has been cited in the provided sources. The advisory is published via Patchstack's vulnerability database. LFI in WordPress themes is a well-known class that attackers do scan for opportunistically once details circulate, so risk should be treated as credible even without confirmed in-the-wild activity.

Researcher notes

CWE-98 LFI with CVSS 8.1 and AC:H suggests exploitation requires specific conditions, but unauthenticated network reachability raises the floor. Affected entry includes versions array of "0" with defaultStatus "unaffected" — treat the authoritative range as the advisory text "from n/a through < 2.6". Patch availability and a fixed version were not stated in the provided bundle; verify with the Patchstack record before recommending a specific upgrade target.

Mitigation direction

  • Inventory WordPress sites for the Karzo theme and identify versions below 2.6.
  • Consult the Patchstack advisory and designervily vendor channels for an official patched release.
  • If no fix is yet available, deactivate or replace the Karzo theme on production sites.
  • Apply WAF rules that block path-traversal patterns and suspicious include parameters.
  • Restrict PHP file system access via open_basedir and least-privilege web user permissions.
  • Rotate any secrets that may have been exposed via wp-config.php or similar files.

Validation and detection

  • Enumerate themes via wp-cli or the admin UI and flag any Karzo install < 2.6.
  • Review web access logs for suspicious query parameters referencing file paths or traversal sequences.
  • Run an authenticated WordPress vulnerability scan that includes Patchstack signatures.
  • Confirm the installed Karzo theme version against the vendor's fixed release once published.
  • Check WAF and edge logs for blocked LFI attempts targeting theme endpoints.
  • Verify file integrity of wp-config.php and other sensitive files for unexpected access patterns.
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-58955 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-58955Attack 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
designervilyKarzokarzo, 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.