LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24593: WordPress AWP Classifieds plugin <= 4.4.3 - Sensitive Data Exposure vulnerability

Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Strategy11 Team AWP Classifieds another-wordpress-classifieds-plugin allows Retrieve Embedded Sensitive Data.This issue affects AWP Classifieds: from n/a through <= 4.4.3.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24593 affects the WordPress AWP Classifieds plugin, also listed as another-wordpress-classifieds-plugin, through version 4.4.3. An unauthenticated remote attacker may be able to retrieve embedded sensitive system information. The documented impact is limited to confidentiality, not site takeover or data modification.

Executive priority

Treat this as a moderate-priority WordPress exposure. It does not indicate full compromise, but unauthenticated information disclosure can aid attackers. Prioritize internet-facing sites using the plugin, especially those handling customer, classified, or operational data.

Technical view

The issue is CWE-497, Exposure of Sensitive System Information to an Unauthorized Control Sphere. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, unchanged scope, low confidentiality impact, no integrity or availability impact. Public details do not specify the exact exposed data or endpoint.

Likely exposure

Exposure is most likely on WordPress sites with AWP Classifieds / another-wordpress-classifieds-plugin installed at version 4.4.3 or earlier. Internet-facing WordPress sites are the primary concern because the CVSS vector requires no authentication or user interaction.

Exploitation context

The source bundle does not indicate active exploitation, and the CVE is not listed as KEV. The vulnerability is remotely reachable and unauthenticated, which lowers attacker effort, but the known impact is limited information disclosure based on available public data.

Researcher notes

Available sources provide classification, affected range, and CVSS but not the vulnerable code path, exposed fields, exploit maturity, or fixed version. Avoid assuming a patch exists from the provided data. Further validation should rely on vendor/Patchstack updates and local plugin inventory.

Mitigation direction

  • Inventory WordPress sites for AWP Classifieds / another-wordpress-classifieds-plugin.
  • Identify installed plugin versions and flag 4.4.3 or earlier.
  • Check Patchstack and vendor guidance for a fixed version or recommended action.
  • Disable or remove the plugin where it is not business-critical.
  • Monitor WordPress and web logs for unusual unauthenticated requests to plugin-related paths.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress site.
  • Record the exact installed plugin version.
  • Compare versions against the affected range: through 4.4.3.
  • Review vendor or Patchstack advisories for remediation status.
  • Document compensating controls if immediate remediation is unavailable.
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 · low confidence lookup

CWE-497: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-2026-24593 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
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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-24593Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Strategy11 TeamAWP Classifiedsanother-wordpress-classifieds-plugin, 0unaffected
Weakness

CWE details

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

CWE-497 · source CWE mapping

Exposure of Sensitive System Information to an Unauthorized Control Sphere

Exposure of Sensitive System Information to an Unauthorized Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.