LiveActive security incident?Get immediate response
CVE Record

CVE-2025-24643: WordPress WPGuppy plugin <= 1.1.0 - Broken Authentication vulnerability

Missing Authorization vulnerability in AmentoTech Private Limited WPGuppy wpguppy-lite allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WPGuppy: from n/a through <= 1.1.0.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-24643 affects the WordPress WPGuppy plugin, package wpguppy-lite, through version 1.1.0. The issue is a missing authorization control that may let an unauthenticated remote actor perform limited unauthorized actions. The recorded impact is medium, with low integrity and availability impact and no stated confidentiality impact.

Executive priority

Prioritize this for WordPress environments using WPGuppy because exploitation requires no login and no user interaction. The recorded business impact is moderate, not critical, but exposed sites should be inventoried and remediated through vendor guidance before routine backlog work.

Technical view

The CVE describes CWE-862 Missing Authorization in AmentoTech WPGuppy wpguppy-lite <= 1.1.0. CVSS 3.1 is 6.5 with AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L, indicating remote, unauthenticated, low-complexity exploitation with limited integrity and availability impact. The bundle does not identify affected endpoints, exploit details, or a fixed version.

Likely exposure

Exposure is limited to WordPress sites that have WPGuppy wpguppy-lite installed at version 1.1.0 or earlier. Sites without this plugin, or with versions outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not report active exploitation, and KEV status is false. It also does not provide proof-of-concept details, exploitation telemetry, or weaponized exploit references. Treat this as a remotely reachable WordPress plugin authorization flaw requiring prompt inventory and vendor-guided remediation.

Researcher notes

Evidence is incomplete for endpoint-level validation: the bundle provides the vulnerability class, affected plugin range, CVSS vector, and Patchstack reference, but not request paths, fixed release information, or exploit artifacts. Avoid assumptions beyond WPGuppy wpguppy-lite <= 1.1.0 until vendor details are confirmed.

Mitigation direction

  • Inventory all WordPress sites for WPGuppy wpguppy-lite installations.
  • Identify any installed WPGuppy versions at 1.1.0 or earlier.
  • Check vendor or Patchstack guidance for a fixed or recommended version.
  • Disable or remove the plugin where no safe vendor-supported option is available.
  • Apply normal WordPress access controls and monitoring around plugin functionality.

Validation and detection

  • Confirm plugin presence and version from WordPress plugin inventory.
  • Verify whether any site runs WPGuppy wpguppy-lite <= 1.1.0.
  • Review vendor and Patchstack entries for updated remediation guidance.
  • Check application logs for unusual unauthenticated access to WPGuppy functionality.
  • Document exposed internet-facing WordPress instances separately from internal-only sites.
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-2025-24643 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
6.5 (3.1)
Known Exploited
No
Published

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

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

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2025-24643Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
AmentoTech Private LimitedWPGuppywpguppy-lite, 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.