LiveActive security incident?Get immediate response
CVE Record

CVE-2025-24552: WordPress Paytium plugin <= 4.4.11 - Full Path Disclosure (FPD) vulnerability

Generation of Error Message Containing Sensitive Information vulnerability in paytiumsupport Paytium paytium allows Retrieve Embedded Sensitive Data.This issue affects Paytium: from n/a through <= 4.4.11.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-24552 is an information disclosure issue in the WordPress Paytium plugin through version 4.4.11. Error messages may expose sensitive embedded data, specifically full server paths. This does not directly allow data modification or service disruption, but it can help attackers understand hosting layout and support follow-on attacks.

Executive priority

Treat this as a moderate-priority WordPress exposure. It is not described as actively exploited and has limited direct impact, but public-facing payment-related plugins should be inventoried and updated or removed promptly.

Technical view

The record describes CWE-209: error messages containing sensitive information in Paytium for WordPress through 4.4.11. CVSS 3.1 is 5.3, with network access, low complexity, no privileges, no user interaction, unchanged scope, and low confidentiality impact. The source bundle does not provide an endpoint, trigger, proof of concept, or fixed release.

Likely exposure

Exposure is likely limited to WordPress sites that have the Paytium plugin installed at version 4.4.11 or earlier. The source bundle does not identify affected configurations beyond the plugin version range.

Exploitation context

No provided source says this is actively exploited, and it is not listed as CISA KEV in the bundle. The CVSS vector indicates remote, unauthenticated reachability, but the documented impact is limited to information disclosure.

Researcher notes

The useful detail is limited: affected product, version range, CWE-209, and CVSS are provided, but no vulnerable route, trigger condition, exploit evidence, or fixed release is included. Avoid assuming broader Paytium compromise from this CVE alone.

Mitigation direction

  • Inventory WordPress sites for the Paytium plugin and installed version.
  • Check Paytium, WordPress.org, and Patchstack guidance for a fixed or recommended version.
  • Disable or remove Paytium where it is not business-critical.
  • Ensure production error display does not reveal server paths.
  • Monitor vendor advisories because the bundle does not name a patch.

Validation and detection

  • Confirm whether Paytium is installed on each WordPress property.
  • Record plugin versions and flag 4.4.11 or earlier for review.
  • Review public error responses for leaked filesystem paths.
  • Check logs and monitoring for repeated error-triggering requests.
  • Verify remediation against current vendor or Patchstack guidance.
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-209: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-24552 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
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

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

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
paytiumsupportPaytiumpaytium, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-209 · source CWE mapping

Generation of Error Message Containing Sensitive Information

Generation of Error Message Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.