LiveActive security incident?Get immediate response
CVE Record

CVE-2025-49910: WordPress WPGuppy plugin <= 1.1.4 - Broken Access Control vulnerability

Missing Authorization vulnerability in AmentoTech Private Limited WPGuppy wpguppy-lite allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WPGuppy: from n/a through <= 1.1.4.

HighCVSS 8.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-49910 affects the WordPress WPGuppy wpguppy-lite plugin through version 1.1.4. The reported issue is broken access control: the plugin exposes functionality without proper authorization checks. Because the CVSS vector indicates no login or user interaction is required, affected public WordPress sites should treat this as a high-priority exposure.

Executive priority

Prioritize within the next patch cycle, sooner for public or customer-facing WordPress sites. The business risk is unauthorized access to plugin functionality and possible exposure of sensitive information. No active exploitation is confirmed in the provided sources.

Technical view

The CVE describes CWE-862 Missing Authorization in AmentoTech Private Limited WPGuppy wpguppy-lite. Scope is unchanged, network exploitable, low complexity, no privileges, no user interaction. Reported impact is high confidentiality and low integrity, with no availability impact. Public sources provided do not describe the specific vulnerable endpoint or a fixed version.

Likely exposure

Exposure is likely limited to WordPress sites running the WPGuppy wpguppy-lite plugin version 1.1.4 or earlier. Internet-facing WordPress sites have higher concern because the CVSS vector is network-accessible and unauthenticated.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. PatchStack is listed as the vulnerability database reference, but the provided data does not include exploit availability, proof-of-concept details, or observed attacks.

Researcher notes

Evidence is limited to the CVE metadata and PatchStack reference. Do not assume affected endpoints, exploit paths, or fixed versions from the provided bundle. Focus validation on asset presence, version confirmation, access-control review, and monitoring for updated vendor disclosures.

Mitigation direction

  • Inventory WordPress sites for the WPGuppy wpguppy-lite plugin.
  • Identify plugin versions and prioritize version 1.1.4 or earlier.
  • Check PatchStack, the vendor, or WordPress plugin repository for official remediation guidance.
  • Update if a vendor-supported fixed version is available.
  • Disable or remove the plugin where it is not business-critical.

Validation and detection

  • Confirm whether wpguppy-lite is installed on each WordPress instance.
  • Record installed plugin version and compare against affected range through 1.1.4.
  • Review web and application logs for unexpected unauthenticated plugin-related requests.
  • Verify remediation by confirming the plugin is updated, disabled, or removed.
  • Monitor vendor and PatchStack entries for newly published technical details.
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-49910 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
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2025-49910Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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