CVE-2024-6554: The Branda – White Label WordPress, Custom Login Page Customizer plugin for WordPress is vulnerable to Full Pa

Q: How do I fix CVE-2024-6554?

branda: upgrade to 3.4.19. Exact commands for each OS are on this page.

Q: Is CVE-2024-6554 being exploited?

CVE-2024-6554 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-6554 affect?

CVE-2024-6554 affects branda. Severity is medium (CVSS 5.3). The Branda – White Label WordPress, Custom Login Page Customizer plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.4.18. This is due the plugin utilizing composer without preventing direct ac

Q: How urgent is CVE-2024-6554?

Priority 33/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADE

CVE-2024-6554 is a medium-severity flaw (CVSS 5.3) affecting branda. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Branda – White Label WordPress, Custom Login Page Customizer plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.4.18. This is due the plugin utilizing composer without preventing direct access to the files. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its o

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 61%)
CISA exploited list	No
Weakness	CWE-200
Published	2024-07-11
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: wpmudev

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-07-11 04:15 UTCPublished CVE record published
2026-06-17 08:18 UTCUpdated Record last modified

wpmudev branda UPGRADE

Affected: < 3.4.19

Fixed in: 3.4.19

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy branda || rpm -q branda || branda --version

2. UPGRADE to 3.4.19 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade branda

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade branda

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-6554?

branda: upgrade to 3.4.19. Exact commands for each OS are on this page.

Is CVE-2024-6554 being exploited?

CVE-2024-6554 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-6554 affect?

CVE-2024-6554 affects branda. Severity is medium (CVSS 5.3). The Branda – White Label WordPress, Custom Login Page Customizer plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.4.18. This is due the plugin utilizing composer without preventing direct ac

How urgent is CVE-2024-6554?

Priority 33/100. Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2024-5191 MEDIUM 6.4 UPGRADE The Branda – White Label WordPress, Custom Login Page Customizer plugin for WordPress is vulnerable to Stored
CVE-2024-37239 MEDIUM 5.9 UPGRADE Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPMU DEV

References

← Back to latest CVEs