# 51567 sc low contract cannot be paused missing public pause and unpause functions **Submitted on Aug 4th 2025 at 04:22:59 UTC by @MMophule for** [**Attackathon | Plume Network**](https://immunefi.com/audit-competition/plume-network-attackathon) * **Report ID:** #51567 * **Report Type:** Smart Contract * **Report severity:** Low * **Target:** * **Impacts:** * Unable to Pause Contract ## Description ### Brief/Intro The contract inherits from the OpenZeppelin `Pausable` contract, but does not implement the required public `pause()` and `unpause()` functions. OpenZeppelin's `Pausable` only provides internal `_pause()` and `_unpause()` functions, so the inheriting contract must expose public functions (usually access-controlled) that call those internals. ### Vulnerability Details Because there are no public `pause()` and `unpause()` functions implemented, the contract cannot be paused via the standard mechanisms provided by OpenZeppelin's `Pausable`. ### Impact Details During potential hacks or black swan events, being unable to pause the contract can prevent administrators from mitigating further harm. This was assessed as medium in impact. ## Proof of Concept The contract and any subcontracts inheriting from it do not include public functions that call `_pause()` and `_unpause()`, so pause/unpause functionality is effectively unavailable. ## Suggested Fix (implicit) Ensure the contract exposes appropriately access-controlled public functions that call `_pause()` and `_unpause()` (for example, `pause()` and `unpause()` guarded by an admin/owner role). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://reports.immunefi.com/plume-or-attackathon/51567-sc-low-contract-cannot-be-paused-missing-public-pause-and-unpause-functions.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.