CVE-2009-5074: Unspecified vulnerability in the MojoX::Dispatcher::Static implementation in Mojolicious before 0.991250 has unknown impact and attack…
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 71.8% of all records.
- No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Unspecified vulnerability in the MojoX::Dispatcher::Static implementation in Mojolicious before 0.991250 has unknown impact and attack vectors.
- Published
- May 2, 2011
- Updated
- Jun 16, 2026
- EPSS
- 1.3% · 71th percentile
- CWE
- —
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| mojolicious | mojolicious | cpe:2.3:a:mojolicious:mojolicious |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- mojolicious mojoliciousup to 0.991246 inclusive
- mojolicious mojolicious0.2
- mojolicious mojolicious0.3
- mojolicious mojolicious0.4
- mojolicious mojolicious0.5
- mojolicious mojolicious0.6
- mojolicious mojolicious0.7
- mojolicious mojolicious0.8
+12 more rows
- mojolicious mojolicious0.8.1
- mojolicious mojolicious0.8.2
- mojolicious mojolicious0.8.3
- mojolicious mojolicious0.8.4
- mojolicious mojolicious0.8.5
- mojolicious mojolicious0.8006
- mojolicious mojolicious0.8007
- mojolicious mojolicious0.8008
- mojolicious mojolicious0.8009
- mojolicious mojolicious0.9
- mojolicious mojolicious0.9001
- mojolicious mojolicious0.9002
Same product
mojolicious: all recordsOther highest-scoring records for the same primary product.
- CVE-2010-4803Mojolicious before 0.999927 does not properly implement HMAC-MD5 checksums, which has unspecified impact and remote attack vectors.41Plan
- CVE-2010-4802Commands.pm in Mojolicious before 0.999928 does not properly perform CGI environment detection, which has unspecified impact and remote…41Plan
- CVE-2024-58134Mojolicious versions from 0.999922 for Perl uses a hard coded string, or the application's class name, as an HMAC session cookie secret by default32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2011-1589Apr 29, 2011 · Directory traversal vulnerability in Path.pm in Mojolicious before 1.16 allows remote attackers to read arbitrary files via a %2f..%2f…21Monitor
- Later →CVE-2011-1841May 2, 2011 · Cross-site scripting (XSS) vulnerability in the link_to helper in Mojolicious before 1.12 allows remote attackers to inject arbitrary web…18Monitor
- Later →CVE-2021-47208Apr 7, 2024 · The Mojolicious module before 9.11 for Perl has a bug in format detection that can potentially be exploited for denial of service.17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
—
CVSS vector
AV:N/AC:L/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.