LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24549: WordPress GeoDirectory plugin <= 2.8.149 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in Paolo GeoDirectory geodirectory allows Cross Site Request Forgery.This issue affects GeoDirectory: from n/a through <= 2.8.149.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24549 is a medium-severity CSRF issue in the WordPress GeoDirectory plugin. If a logged-in site user with relevant access is tricked into an action, an attacker may cause an unintended state-changing request. Business impact appears limited to integrity, not data theft or service outage, based on the provided CVSS vector.

Executive priority

Treat as a routine but timely WordPress plugin remediation. Prioritize internet-facing business sites using GeoDirectory, especially sites with many administrators or editors. There is no provided evidence of active exploitation or severe impact.

Technical view

The CVE describes CWE-352 Cross-Site Request Forgery in Paolo GeoDirectory for WordPress, affecting versions through 2.8.149. CVSS 3.1 is 4.3: network attack vector, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact, no confidentiality or availability impact.

Likely exposure

Exposure is likely limited to WordPress sites running the GeoDirectory plugin at affected versions, reported as through 2.8.149. The provided Patchstack reference URL mentions 2.8.147, so version details should be verified against vendor or Patchstack records.

Exploitation context

No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV. Exploitation requires user interaction, consistent with CSRF, typically involving a logged-in victim being induced to perform an unintended request.

Researcher notes

The source bundle contains a version inconsistency: the CVE title and description say affected through 2.8.149, while the Patchstack URL references 2.8.147. No specific fixed version or mitigation is provided in the bundle. Avoid assuming exploitability beyond CSRF requiring user interaction.

Mitigation direction

  • Inventory WordPress sites using the GeoDirectory plugin.
  • Check installed GeoDirectory versions against the CVE and Patchstack entry.
  • Follow GeoDirectory or Patchstack guidance for the fixed version when available.
  • Apply the vendor-recommended update or mitigation after testing.
  • Limit administrative access and require careful review of unsolicited links.

Validation and detection

  • Confirm whether GeoDirectory is installed on each WordPress site.
  • Record the installed plugin version from WordPress administration or asset inventory.
  • Compare versions to the affected range through 2.8.149.
  • Review vendor or Patchstack advisories for fixed-version confirmation.
  • Monitor web logs for suspicious state-changing requests from authenticated sessions.
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-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-24549 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-24549Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
PaoloGeoDirectorygeodirectory, 0unaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.