CVE-2012-0895
Overview
CVE-2012-0895 is a known-severity vulnerability affecting tom_braider count_per_day. It was published on January 20, 2012.
Technical Description
Cross-site scripting (XSS) vulnerability in map/map.php in the Count Per Day module before 3.1.1 for WordPress allows remote attackers to inject arbitrary web script or HTML via the map parameter.
Remediation
Check the references section for vendor advisories and patches from tom_braider. Update count_per_day to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| tom_braider | count_per_day | 0 | Affected |
References
Frequently Asked Questions
What is CVE-2012-0895?
CVE-2012-0895 is a known-severity vulnerability affecting tom_braider count_per_day. It was published on January 20, 2012.
How severe is CVE-2012-0895?
CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.
How do I fix or remediate CVE-2012-0895?
Check the references section for vendor advisories and patches from tom_braider. Update count_per_day to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2012-0895?
CyberStrike's AI-powered security agents can automatically detect CVE-2012-0895 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.