LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25012: WordPress WP Bannerize Pro plugin <= 1.11.0 - Broken Access Control vulnerability

Missing Authorization vulnerability in gfazioli WP Bannerize Pro wp-bannerize-pro allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Bannerize Pro: from n/a through <= 1.11.0.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25012 affects the WordPress WP Bannerize Pro plugin through version 1.11.0. The issue is broken access control: the plugin may expose data because authorization checks are missing or misconfigured. The published score is medium, with limited confidentiality impact and no cited integrity or availability impact.

Executive priority

Treat this as a moderate WordPress plugin exposure. It does not indicate system takeover, but unauthenticated data exposure risk can still affect privacy, compliance, and brand trust. Prioritize internet-facing WordPress sites and confirm whether the plugin is present.

Technical view

The CVE describes CWE-862 Missing Authorization in gfazioli WP Bannerize Pro, package wp-bannerize-pro, versions through 1.11.0. CVSS 3.1 is 5.3: AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N. Sources do not provide endpoint-level details, proof-of-concept information, or a named fixed version.

Likely exposure

Exposure is limited to WordPress sites running WP Bannerize Pro version 1.11.0 or earlier. The CVSS vector indicates the issue is remotely reachable without authentication or user interaction, but only low confidentiality impact is documented.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not listed as KEV in the supplied bundle. The available public details are sparse, so defenders should avoid assuming exploitability beyond the published CVSS and vulnerability class.

Researcher notes

The source bundle identifies missing authorization but omits affected endpoints, vulnerable actions, and remediation version. Do not infer exploit mechanics. Useful next steps are version verification, monitoring for vendor/Patchstack updates, and controlled validation that avoids publishing weaponizable details.

Mitigation direction

  • Inventory WordPress sites for WP Bannerize Pro installations.
  • Identify installed WP Bannerize Pro versions and flag 1.11.0 or earlier.
  • Check Patchstack and vendor guidance for an updated or remediated version.
  • Restrict or remove the plugin if no safe update is available.
  • Review web access logs for unusual unauthenticated requests to plugin functionality.

Validation and detection

  • Confirm whether WP Bannerize Pro is installed on each WordPress site.
  • Record the exact plugin version from WordPress administration or asset inventory.
  • Compare findings against affected versions through 1.11.0.
  • Verify whether vendor or Patchstack guidance identifies a fixed release.
  • Document compensating controls if the plugin cannot be updated or removed.
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-2026-25012 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-25012Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
gfazioliWP Bannerize Prowp-bannerize-pro, 0unaffected
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.