Thursday, March 6, 2025
HomeCVE/vulnerabilityLibreOffice Flaw Allows Attackers to Run Arbitrary Scripts via Macro URL

LibreOffice Flaw Allows Attackers to Run Arbitrary Scripts via Macro URL

Published on

SIEM as a Service

Follow Us on Google News

A significant security vulnerability in LibreOffice, designated as CVE-2025-1080, has been patched in versions 24.8.5 and 25.2.1, released on March 4, 2025.

The flaw, which allowed attackers to execute arbitrary scripts through manipulated macro URLs, posed a severe risk to users of the open-source office suite.

This vulnerability underscores the importance of prompt software updates in enterprise and personal computing environments.

Technical Breakdown of CVE-2025-1080

The vulnerability stems from LibreOffice’s implementation of Office URI Schemes, a feature designed to facilitate browser integration with Microsoft SharePoint servers.

While this functionality enables seamless document collaboration, researchers identified a critical oversight in LibreOffice’s custom vnd.libreoffice.command URI scheme.

In affected versions (prior to 24.8.5 and 25.2.1), attackers could craft specialized links containing embedded inner URLs.

When clicked, these malicious links bypassed security protocols and triggered internal LibreOffice macros with unauthorized arguments.

Security analyst Amel Bouziane-Leblond, who discovered the vulnerability, noted that “the URI handler failed to properly sanitize nested URL components, creating an execution pipeline for untrusted code.”

This exploitation mechanism could occur without user interaction beyond clicking a link in a web browser.

The flaw effectively transformed ordinary document-sharing workflows into potential attack vectors, particularly dangerous in organizations using SharePoint-integrated collaboration systems.

Mitigation and Patching Requirements

LibreOffice maintainers addressed the vulnerability through enhanced URI validation protocols in the updated releases. The patch introduces multiple security checks:

  • Strict schema verification for nested URL components
  • Macro execution confirmation dialogs for all command-based URI triggers
  • Sandboxing of URI-handler processes

“These changes ensure command URIs adhere to strict formatting rules while maintaining compatibility with legitimate SharePoint integrations,” explained Caolán McNamara of Collabora Productivity, who led the patching effort.

Organizations unable to immediately upgrade should disable LibreOffice’s browser integration features through Group Policy settings or application hardening tools.

This discovery highlights the evolving security challenges in cross-platform productivity software.

Researchers and maintainers urge users to maintain vigilance against social engineering tactics that could amplify technical vulnerabilities.

The coordinated disclosure between independent security researchers and LibreOffice developers demonstrates effective open-source community responses to emerging threats.

Collect Threat Intelligence on the Latest Malware and Phishing Attacks with ANY.RUN TI Lookup -> Try for free

Divya
Divya
Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Latest articles

Sitecore Zero-Day Flaw Allows Remote Code Execution

A critical zero-day vulnerability in Sitecore’s enterprise content management system (CMS) has been uncovered,...

Apache Airflow Misconfigurations Leak Login Credentials to Hackers

A recent investigation into misconfigured Apache Airflow instances has uncovered critical vulnerabilities exposing login...

Two Cybercriminals Arrested for ATM Jackpotting Scheme

Federal authorities have unveiled details of a sophisticated cybercrime operation targeting financial institutions across...

Black Basta’s Notorious Tactics and Techniques Exposed in Leaked Intel

A significant leak of internal chat logs from the Black Basta ransomware group has...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Sitecore Zero-Day Flaw Allows Remote Code Execution

A critical zero-day vulnerability in Sitecore’s enterprise content management system (CMS) has been uncovered,...

Apache Airflow Misconfigurations Leak Login Credentials to Hackers

A recent investigation into misconfigured Apache Airflow instances has uncovered critical vulnerabilities exposing login...

Two Cybercriminals Arrested for ATM Jackpotting Scheme

Federal authorities have unveiled details of a sophisticated cybercrime operation targeting financial institutions across...