Categories
CVE-2026-7105 medium CVSS 4.3

Vulnerability in Xpro Addons (WordPress plugin) (CVE-2026-7105)

Summary

Vulnerability in Xpro Addons (WordPress plugin) (CVE-2026-7105). Risk of unauthorized operations or information disclosure. Exploitable via xpro_content.

Original description

The description as published by the source.

The Xpro Addons plugin for WordPress is vulnerable to unauthorized creation of data due to a missing capability check on the get_menu_content_editor() function in all versions up to, and including, 1.5.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create arbitrary published posts of the xpro_content custom post type with attacker-controlled titles. The created posts are publicly queryable on the front-end, enabling content injection, SEO spam, and database pollution.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-7105 has been found in Xpro Addons (WordPress plugin).
Attackers can target a specific entry point like xpro_content over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Xpro Addons (WordPress plugin) CVE-2026-7105" on the vendor's site.

CVE-2026-7105 (Xpro Addons (WordPress plugin)) — CWE-862 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: xpro_content
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-862) exists in Xpro Addons (WordPress plugin). Attackers reach the vulnerable code path via xpro_content.

📍 Affected scope

Check the vendor advisory for the affected versions of Xpro Addons (WordPress plugin). Attack surface: xpro_content.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Xpro Addons (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details