Vulnerabilities exploited in the wild must be reported within 24 hours, who should submit this report
Who is affected by this new rule requiring the reporting of vulnerabilities exploited in the wild, and what report do website operators need to submit? The obligation lies with manufacturers placing products with numerical elements in the EU market, as well as open-source software maintainers under specific conditions, not with every operator of a site. Most domestic sites are not within the jurisdiction, but this set of three-time limits is worth borrowing for your own emergency rhythm.
When does the new regulation take effect
The obligation to report rules will start to apply from September 11th of this year, the triggering conditions are two types of events: vulnerabilities being exploited in the wild, and major events affecting product safety. That is to say, having 'vulnerabilities' does not necessarily trigger reporting; whether they have been exploited, and whether they affect safety, is the starting point for judgment.
What is due for each of the three time limits
| Time limit | What is exchanged | Content focus | Common gaps |
|---|---|---|---|
| Twenty-four hours | Early warning | Initial judgment on the existence and impact of the event | Report only after the root cause is found |
| Seventy-two hours | Vulnerability or event announcement | Technical details, exploitation status | No distinction of affected versions |
| Within fourteen days | Final report | Rectification measures and root causes | Rectification and release immediately archived, no root cause written |
First tier must be provided within 24 hours after awareness of the event, the second tier should provide more complete information, and the third tier should submit the final report within fourteen days after the implementation of available rectification measures. The difference between the three tiers is not that 'the longer the writing, the better', but that it answers three different questions: Did an incident occur, what was the impact, and how to completely fix it.
Who is considered as a party that needs to be reported
The entity responsible for declaring is the manufacturer of the product, including the主体 that combines hardware, software, and cloud services to enter the market; the maintainer of open-source software assumes its own declaration obligations within the rules, but the scope is different from that of commercial manufacturers.
The operator of the site is usually in the position of a 'user': you do not constitute a manufacturer, but the systems and plugins you rely on belong to the regulated products. What truly affects the operator is indirect obligations - once the declaration is initiated upstream, the pace of repairs and the disclosure of information will be faster, and your emergency window will be compressed accordingly.
What can unregulated sites do with this time limit?
Treat the three-level time limit as an internal handling rhythm, which is a very useful organizational method.
- Discover vulnerabilities that are being exploited in the wild: complete the initial assessment of the impact within 24 hours and communicate with the outside world, clearly stating which sites are affected;
- Within 72 hours: complete the list of affected versions, exposure surface, and judgment of whether there are already intrusion traces, and form a notification report;
- Within 14 days after the measures are available: write the root cause and corrective conclusion, and archive it to the operation and maintenance records.
The complementary capabilities on the self-built system side are equally important. AnQiCMS in the v3.6.6 release notes also handled two high-risk issues of list sorting parameter injection and the login credentials of site switching being forgeable, and provided subsequent actions such as rotating site signature configuration and changing the administrator password. Such entries of 'changing credentials after repair' correspond to the final report phase in the timeline.When integrating with automation, the MCP interface sets the exposure range based on the intent domain, operations such as backup, upgrade, and multi-site are default closed at the site-wide level; write operations are merged and confirmed at the round level to avoid being executed by automation scripts in the emergency window.External AI clients such as Claude, Cursor can access this interface, but the approval process remains on the human side.
Four things fall on the daily duty shift.
- Subscribe to the announcement source of the dependent system, don't wait until the vulnerability is already in the wild to know about the announcement.
- Write the clear duty rules for 'who has the authority to shut down the public entry point'.
- Each handling should leave a timestamp, and the final report is directly assembled from it;
- Practice a 24-hour and 72-hour window, to see if the internal process can keep up.
Common questions
I am just the operator, do I need to report to the regulator?Generally, it is not necessary, the rules govern the manufacturer and the maintenance party; the operator's action is to convert the upstream announcement into internal handling.
When does the 24-hour period start?Start from the time of realization of the event, not from the time of identifying the root cause, this is the significance of early warning.
What should be done if the deadline is missed?Record the reasons for delay and remedial actions, the regulator is concerned about the effectiveness of the process, and it is more beneficial to keep a complete record after the event than to conceal it.
Is it necessary to be so tight with the internal rhythm?In scenarios with the risk of being exploited in the wild, the shorter the window, the less exposure time can be reduced; common defects do not need to be covered with the same strength.