LiveActive security incident?Get immediate response
CVE Record

CVE-2025-10308: Astro Booking Engine <= 1.4.0 - Cross-Site Request Forgery to Settings Reset

The Astro Booking Engine plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4.0. This is due to missing nonce validation on the options deletion functionality. This makes it possible for unauthenticated attackers to delete all plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

MediumCVSS 4.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A malicious party could trick a logged-in WordPress administrator into clicking a crafted link that resets all Astro Booking Engine settings. The attacker needs no account, but administrator interaction is required. The issue can disrupt booking configuration; the supplied scoring indicates no direct data theft or full site compromise.

Executive priority

Schedule prompt remediation for affected booking sites, prioritizing systems whose configuration loss would interrupt customer bookings. This is not an emergency comparable to remote code execution, but administrators can be targeted without attacker credentials and a successful reset may cause operational disruption.

Technical view

Astro Booking Engine through version 1.4.0 lacks nonce validation in its options-deletion function, enabling cross-site request forgery. An unauthenticated attacker can submit a forged settings-reset request through an administrator’s browser. CVSS 3.1 is 4.3: network-accessible, low complexity, no privileges, user interaction required, with low integrity impact.

Likely exposure

WordPress sites using Astro Booking Engine version 1.4.0 or earlier are potentially exposed, particularly while administrators are authenticated. The supplied structured affected-version metadata is inconsistent with the narrative, so asset owners should verify installed versions and vendor guidance directly.

Exploitation context

The bundle does not establish active exploitation, and the CVE is not listed as KEV. Successful abuse requires social engineering or another method of inducing a logged-in administrator to perform the forged action. Evidence supports settings deletion only, not confidentiality loss, code execution, or complete site takeover.

Researcher notes

The weakness maps to CWE-352. The supplied code reference shows the relevant support-tab logic, while the changeset indicates a corrective code change; however, the bundle does not explicitly name the first fixed release. The structured affected entry lists version “0” with default status “unaffected,” conflicting with the narrative range through 1.4.0.

Mitigation direction

  • Identify WordPress sites running Astro Booking Engine and record each installed version.
  • Check the plugin’s current vendor guidance and update to a release containing the nonce-validation correction.
  • Disable or remove the plugin where it is unnecessary or no corrected release is available.
  • Restrict administrator browsing and avoid opening untrusted links while authenticated to WordPress.

Validation and detection

  • Confirm the installed Astro Booking Engine version on every WordPress instance.
  • Review the referenced changeset and verify the deployed release includes nonce validation for settings deletion.
  • Test settings-reset requests safely in staging to confirm invalid or absent nonces are rejected.
  • Check whether booking settings changed unexpectedly and review relevant WordPress administrative logs where available.
Prepared
Confidence
medium
Sources
4

Public sources used

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-2025-10308 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
5Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Wordfence

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2025-10308Attack 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

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. Source timelineWordfence

    Vendor Notified

  3. Source timelineWordfence

    Disclosed

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

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

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
alianAstro Booking Engine0unaffected
Weakness

CWE details

CWE-352

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.

Open CWE intelligenceSame-CWE CVEs