dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-39583

HIGH · 7.1 CVSS v3.1 Published 2025-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Missing Authorization vulnerability in Bertha AI – Andrew Palmer BERTHA AI bertha-ai-free allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects BERTHA AI: from n/a through <= 1.12.10.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Missing Authorization vulnerability in the Bertha AI WordPress plugin (free version, versions up to 1.12.10.2) allows attackers to exploit incorrectly configured access control security levels, likely enabling unauthorized access to administrative functions or sensitive data without proper authentication.

MitigationUpdate to a patched version of the Bertha AI plugin once available, or implement proper authorization checks for all sensitive endpoints and functions within the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Bertha AI plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'bertha-ai' or similar
    Affected if The Bertha AI plugin (free version) is present in the WordPress installation
  2. Identify the installed version number
    In WordPress admin, view the plugin details to see the version number, or open the main plugin file (usually bertha-ai.php) and check the 'Version' header in the plugin comment block
    Affected if The version displayed is 1.12.10.2 or any version lower than 1.12.10.2
  3. Compare version against affected range
    Compare your installed version to the affected range: versions up to and including 1.12.10.2 are vulnerable
    Affected if Your installed version is 1.12.10.2 or earlier (the free version of Bertha AI)
  4. Verify the vulnerability is exploitable
    Since this is a missing authorization flaw, the vulnerability exists simply by having the plugin installed with an affected version - no specific configuration toggle is required for the flaw to apply
    Affected if The plugin is active and running an affected version (1.12.10.2 or lower)

You are affected if the Bertha AI WordPress plugin (free version) is installed and the installed version is 1.12.10.2 or any earlier version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the Bertha AI plugin once available, or implement proper authorization checks for all sensitive endpoints and functions within the plugin.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-39583 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-39583 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data