CVE-2025-63018
Unknown Unknown - Not Provided

BaseFortify

Vulnerability report for CVE-2025-63018, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-01-22

Last updated on: 2026-04-27

Assigner: Patchstack

Description

Missing Authorization vulnerability in wproyal Bard bard allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Bard: from n/a through <= 2.229.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-01-22
Last Modified
2026-04-27
Generated
2026-07-06
AI Q&A
2026-01-22
EPSS Evaluated
2026-07-05
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
patchstack bard to 2.229 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2025-63018 is a broken access control vulnerability in the WordPress Bard Theme up to version 2.229. It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which allows users with low-level privileges (Subscriber-level) to perform actions that should be restricted to higher-privileged roles like Developers. [1]

Impact Analysis

This vulnerability can allow unprivileged users to perform actions reserved for higher-privileged roles, potentially leading to unauthorized changes or access within the WordPress Bard Theme. However, it is considered low severity with a CVSS score of 4.3 and is unlikely to be exploited. No official fix is currently available, but mitigation services are offered by Patchstack. [1]

Detection Guidance

Detection involves checking for unauthorized access attempts or privilege escalations within the WordPress Bard Theme up to version 2.229. Since the vulnerability allows Subscriber-level users to perform Developer-level actions due to missing authorization checks, monitoring logs for such privilege misuse is key. Specific commands are not provided in the resources, but general approaches include reviewing WordPress user role activity logs and using security plugins or tools that monitor access control anomalies. [1]

Mitigation Strategies

Immediate mitigation steps include restricting Subscriber-level user permissions to prevent unauthorized actions, applying any available mitigation services offered by Patchstack, and monitoring for suspicious activity. Since no official fix or patched version is currently available, applying compensating controls such as enhanced access monitoring and limiting user capabilities is recommended. [1]

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-63018. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart